1 ATS Routes and Upper Control Areas (UTA)
1.1 ATS Routes — Description
1.1.1 ATS Routes are predicated upon significant geographical points which may or may not coincide with the location of a radio navigation aid. These significant points are shown in column 1 of the table depicted in ENR 3. Any coincident radio navigation aid is depicted immediately underneath.
1.1.2 Except where stated otherwise the width of an Airway is 5 NM either side of a straight line joining each two consecutive points shown in column 1 of the table. Upper ATS Routes have no declared width but for the purposes of ATS provision are deemed to be 5 NM either side of a straight line joining each two consecutive points. The vertical extent is shown in column 3 of the table. Where lower limits of Airways are defined as Flight Levels an absolute minimum altitude of 3001 FT applies unless otherwise stated in column 3 and the minimum cruising level shown in column 5 may not always be available.
1.1.3 Unless otherwise stated the ATS Routes catalogued in the table in ENR 3 are designed to contain aircraft navigating to RNAV 5 (ICAO DOC 9613 - AN/937 refers).
1.1.4 The ATS Route network is hereby notified for the purposes of the UK Air Navigation Order.
1.1.5 When an ATS Route transits a TMA, the status of the TMA takes precedence in airspace classification and conditions of use. Aircraft filed to fly on an ATS route that transits a TMA are required to be a minimum of RNAV 5 compliant.
1.1.6 CDR - A route which is permanently plannable during the times published in ENR 3 and may be used tactically at the discretion of ATC. Conditional routes (CDRs) are non-permanent ATS routes. They are designed to complement the permanent ATS route network and to allow flights to be planned on ATS routes, or portions thereof, that are not always available.
In the ATS route tables hereafter the CDR category is indicated under “Route availability” as “CDR” and is permanently plannable during the times published in the AIP. Due to military or other activities, the route may be closed. The unavailability is published daily in the EAUP/EUUP (European airspace use plan/European updated airspace use plan) in table “ATS Route and CDR Type 1 Closure”. The EAUP/EUUP is published on the Network Portal (NOP): https://www.public.nm.eurocontrol.int/PUBPORTAL/. In the event of a short notice unavailability of a CDR, rerouting around an associated AMC-Manageable Area will be made on ATC instructions.
1.1.7 In addition to published ATS routes, specific direct (DCT) options are allowed via the RAD Appendix 4. Specified DCT routes connecting the Reykjavik/Scottish boundary points and the UK Upper ATS route network should be used when flight planning to cross 61N between 000E and 006W.
1.2 ATS Route Designators
1.2.1 In accordance with ICAO Annex 11, the following prefix designators are used to indicate European Regional RNAV Routes, L, M, N, P and for non Regional RNAV Routes Q, T, Y, Z. Routes designated with these prefixes are compulsory RNAV at all levels except when otherwise notified.
1.3 Free Route Airspace
1.3.1 Free Route Airspace (FRA) is a volume of airspace in which the ATS route structure has been removed allowing operators to flight plan any DCT route option of their choosing between specific FRA entry/exit/arrival/departure and published intermediate waypoints.
FRA lateral and vertical limits are included in ENR 2.2 and depicted at ENR 6-70.
1.4 Airspace Security Warnings by the Department for Transport
1.4.1
Introduction
1.4.1.1 Security advice to UK air operators by government is issued in the form of a NOTAM to provide guidance or direction on airspace security risks. Longer term, ongoing warnings are included within the UK Aeronautical Information Publication (AIP). The DfT has developed an Airspace Security Warning Protocol that culminates in the issue of an airspace security warning as V Series NOTAM. Most of these NOTAMs will relate to potential risks to civil aircraft from surface-to-air missiles. However, the use of a NOTAM could also be for other security related threats that may arise.
1.4.2
Information
1.4.2.1 The opening text of the NOTAM takes the form: “SECURITY - HAZARDOUS SITUATION [COUNTRY/IES]”. The NOTAM will clearly specify the particular FIR(s) affected, and, where appropriate, give more precise details of the geographic area of concern, using coordinates, or by other means of demarcation (e.g. “...IN THE xxxx FIR, EAST OF 0310000E”). This will be followed by a brief description of the type of threat, e.g. “POTENTIAL RISK FROM ANTI-AIRCRAFT WEAPONRY”.
1.4.2.2 Where the potential risk is from Man-Portable Air Defence Systems (MANPADS), there is likely to be a restriction on flying below 25,000 FT AGL. Where there is a potential threat from air defence systems with a greater operational ceiling, this is likely to be 'Surface to Unlimited'. In the case of a threat from missiles, it is possible to extend their effective ceiling by launching from elevated terrain. For that reason, most height restrictions stated in an airspace security risk NOTAM will be noted as ‘Above Ground Level’ (AGL).
1.4.3
Guidance
1.4.3.1 Following the information on location and threat, there will (usually) be one of 3 forms of wording employed in expressing DfT’s guidance to operators:
“UK CIVIL AIR OPERATORS ARE ADVISED TO TAKE POTENTIAL RISK INTO ACCOUNT [IN FIR NAME] / WITHIN THE TERRITORY AND AIRSPACE OF [COUNTRY]”.
“UK CIVIL AIR OPERATORS ARE RECOMMENDED NOT TO ENTER THE [FIR NAME] / TERRITORY AND AIRSPACE OF [COUNTRY]”.
“IN ACCORDANCE WITH DIRECTION UNDER THE AVIATION SECURITY ACT 1982 UK CIVIL AIR OPERATORS SO SERVED ARE PROHIBITED TO ENTER THE [FIR NAME] / TERRITORY AND AIRSPACE OF THE STATE OF [COUNTRY]”.
1.4.3.2 The wording will generally follow the patterns above, but could vary as, e.g., it may not always be possible to specify the precise nature of a potential security risk to aircraft, or, the geographic area may be complex to describe.
1.4.3.3 DfT will review the content of the NOTAM 60 days from the date of issue, 30 days prior to its expiry. Due to the evolving and fluid nature of many conflicts, NOTAMs may be extended for a further 90 days if appropriate. Advice which is to remain in place beyond this will in most cases be moved into the AIP..
1.4.3.4 UK civil air operators planning to operate in airspace covered by DfT NOTAMs or AIP entries are strongly encouraged to contact DfT in advanced of operating to ensure they have the latest available information to inform the air carriers own risk assessment.
1.4.3.5 Queries can be made to:
Global Risk & Response Team, Aviation Security Division: +44 (0)207-082 6639, Mon-Fri 0830-1630 (0730-1530);
If urgent, out of hours the Aviation Security Duty Officer can be contacted via +44 (0)207-944 3111.
1.4.4
International Co-ordination
1.4.4.1 The International Civil Aviation Organisation (ICAO) has established a website from which links are available to relevant information from any participating State source to support the assessment of risks over conflict zones. As part of the UK’s contribution to this ICAO initiative, all UK NOTAMs relating to conflict zone issues will be made available on the AIS Website, to which a link will be provided from the ICAO website.
1.4.4.2 It is possible that other States’ advice may differ from that provided by the UK. UK NOTAMs or AIP entries concerning conflict zones represent the best advice available from UK Government sources in support of airline risk assessments. Nonetheless, if operators are concerned about advice from other States that conflicts with, or does not align with, that issued by the UK they should contact DfT on the numbers provided above.
1.4.5
Current Airspace Warnings
|
Serial
|
Location
|
Text
|
Lower Altitude
|
Upper Altitude
|
Date of Issue
|
|
1
2
|
(Gulf of) Aqaba
|
Security - Hazardous Situation in Gulf of Aqaba
UK civil air operators are advised to take risk into account when operating up to 150 NM from the centre point of the Gulf of Aqaba (calculated to be 284536N 344236E) due to potential risk from heightened military activity.
|
Surface
|
Unlimited
|
26 Dec 24
|
|
2
3
|
Belarus
|
Security - Hazardous Situation in Belarus
UK civil air operators are recommended not to enter FIR MINSK (UMMV). Potential safety and security risks.
|
Surface
|
Unlimited
|
24 Jan 22
|
|
3
4
|
Iran
|
Security - Hazardous Situation in Iran
UK civil air operators are recommended not to enter FIR TEHRAN (OIIX). Potential risk from anti-aircraft weaponry and heightened military activity.
|
Surface
| Unlimited | 03 Oct 24 |
|
4
5
|
Haiti
|
Security - Hazardous Situation in Haiti
UK civil air operators are recommended not to enter FIR PORT-AU-PRINCE (MTEG) below 10,000 FT AGL due to potential risk to aviation from small arms fire.
|
Surface
| 10,000 FT AGL | 15 Nov 24 |
|
5
6
|
Iraq
|
Security - Hazardous Situation in Iraq
UK civil air operators are recommended not to enter FIR BAGHDAD (ORBB) below FL 320. Potential risk from anti-aircraft weaponry.
|
Surface
|
FL 320
|
12 Sep 22
|
|
6
7
|
Libya
|
Security - Hazardous Situation in Libya
In accordance with Direction under the Aviation Security Act 1982, UK civil operators so served are prohibited to enter FIR TRIPOLI (HLLL) / the territory and airspace of the State of Libya. Potential risk from anti-aircraft weaponry.
UK operators not currently subject to direction under the Aviation Security Act should contact UK Department for Transport (DfT) before operating in this area.
|
Surface
|
Unlimited
|
12 Jun 15
|
|
7
8
|
Mali
|
Security - Hazardous Situation in Mali
UK civil air operators are advised to take potential risk into account within FIR NIAMEY (DRRR) and FIR DAKAR (GOOO) within the territory and airspace of Mali. Potential risk from anti-aircraft weaponry.
|
Surface
|
Unlimited
|
17 Mar 23
|
|
8
9
| Myanmar |
Security - Hazardous Situation in Myanmar
UK civil air operators are advised to take potential risk into account when operating below 25,000 FT above ground level (AGL) in FIR YANGON (VYYF). Potential risk from anti-aircraft weaponry.
|
Surface
| 25,000 FT AGL |
15 May 25
|
|
9
10
|
North Korea / Sea of Japan
|
Security - Hazardous Situation in North Korea / Sea of Japan
UK civil air operators are recommended not to enter FIR PYONGYANG (ZKKP) and are advised to take potential risk into account over the Sea of Japan (within the geographical coordinates of 1280000E and 1400000E degrees of longitude). Potential risk from unannounced missile tests.
|
Surface
|
Unlimited
|
23 Aug 17
|
|
10
11
|
Red Sea
|
Security - Hazardous Situation in the Red Sea
UK civil air operators are advised to take potential risk into account when operating over the waters of the Red Sea due to potential risk from heightened military activity.
|
Surface
|
Unlimited
|
26 Dec 24
|
|
12
11
|
Somalia
|
Security - Hazardous Situation in Somalia
UK civil air operators are recommended not to enter FIR MOGADISHU (HCSM) below 25,000 FT above ground level (AGL). Potential risk from anti-aircraft weaponry.
|
Surface
| 25,000 FT AGL |
15 Jan 16
|
|
13
12
|
Sudan
|
Security - Hazardous Situation in Sudan
UK civil air operators are recommended not to enter FIR KHARTOUM (HSSS) within the territory and airspace of Sudan. Potential risk from anti-aircraft weaponry and heightened Military activity.
|
Surface
|
Unlimited
| 21 Apr 23 |
|
14
13
|
South Sudan
|
Security - Hazardous Situation in South Sudan
UK civil air operators are advised to take potential risk into account within FIR KHARTOUM (HSSS) within the territory and airspace of South Sudan below 25,000 FT above ground level (AGL). Potential risk from anti-aircraft weaponry.
|
Surface
|
25,000 FT AGL
| 12 Jun 15 |
|
14
15a
|
Syria
|
Security - Hazardous Situation in Syria
In accordance with Direction under the Aviation Security Act 1982, UK civil operators so served are prohibited to enter FIR DAMASCUS (OSTT) / territory and airspace of the Syrian Arab Republic. Potential risk from anti-aircraft weaponry.
UK operators not currently subject to direction under the Aviation Security Act should contact UK Department for Transport (DfT) before operating in this area.
|
Surface
|
Unlimited
| 12 Jun 15 |
|
1
1
4
5b
|
(Vicinity of) Syria
|
Security - Hazardous Situation in Vicinity of Syria
UK civil air operators are advised to take potential risk into account when operating up to 200 NM outside FIR DAMASCUS (OSTT). Potential risk from anti-aircraft weaponry.
|
Surface
|
Unlimited
| 22 Oct 18 |
|
15
16
|
Ukraine
|
Security - Hazardous Situation in Ukraine
In accordance with Direction under the Aviation Security Act 1982, UK registered air operators so served are prohibited to enter FIR LVIV (UKLV), FIR SIMFEROPOL (UKFV), FIR ODESA (UKOV), FIR KYIV (UKBV) and FIR DNIPROPETROVSK (UKDV) / territory and airspace of Ukraine. Potential risk from anti-aircraft weaponry and heightened military activity.
UK operators not currently subject to direction under the Aviation Security Act should contact UK Department for Transport (DfT) before operating in this area.
|
Surface
|
Unlimited
| 24 Feb 22 |
16
17
| Yemen |
Security - Hazardous Situation in Yemen
UK civil air operators are recommended not to enter FIR SANAA (OYSC). Potential risk from anti-aircraft weaponry. Excluded from this recommendation are airways N315, UL425 and R401.
|
Surface
|
Unlimited
| 08 Sep 15 |
1.5 Flight Planning Restrictions
1.5.1 Flight planning restrictions applicable to UK airspace are published within the
DNM RAD (a pre-flight ATFCM Tool). UK restrictions are contained within the UK Annex (Annex EG) as well as Appendices 2, 3, 4, 5 and 6 which can be found via the DNM NOP Portal website within the RAD Home page section -
https://www.nm.eurocontrol.int/RAD/
1.5.1.1 Changes to the RAD are published in line with the AIRAC cycle. Any changes required between AIRAC Cycle publication dates, due to urgent operational reasons, will be notified by NOTAM.
1.5.1.2 Operators should refer to the RAD and its various appendices when constructing routes for an IFR flight within or overflying UK airspace.
1.5.2 For information on standard routings within UK airspace, and alternative routings during CDR closures, users should refer to the
United Kingdom & Ireland Standard Route Document (SRD) as published via the UK AIS CD-ROM (bespoke database and Adobe PDF formats) or via the DNM NOP Portal RAD Homepage within the 'Additional Documentation' section.
1.5.2.1 The United Kingdom & Ireland SRD is issued in line with the AIRAC cycle and is available to assist aircraft operators in constructing RAD compliant UK and Irish portions of IFR flight plannable routes. The route listings contained should be considered as 'preferred' and are not mandatory, however they are promulgated to identify optimum routings for operators with due regard for the ATC system. Reference may be made to applicable RAD restrictions for a route, details of which may be found via the DNM NOP Portal RAD Home page website.
1.5.3 Temporal flight planning buffers are added to Special Use Airspace (SUA) activation times in order to allow for flights departing late (or early) on their scheduled ETD. The parent Area Control Centre Airspace Management Cell (AMC) define the buffer requirement and parameters during the airspace planning phase of Airspace Management.
When SUA areas are active, the AUP published activation time includes temporal buffer at the start and end of the activity. No extra buffer is required for flight planning purposes. SUA activation NOTAM define the actual parameters of the activity and do not include any element of a temporal flight planning buffer, therefore the NOTAM start and end time of the actual activity will be different to the AUP times.
1.6 Rules and Procedures
1.6.1
Control Areas (Airways)
1.6.1.1
Radio Communications and Equipment
1.6.1.1.1 The requirements for radio communications and equipment are set out in GEN 1.5.
1.6.1.2
ATC Clearance
1.6.1.2.1 One of the following phrases may be included in the initial clearance when the air traffic situation necessitates the regulation of departing flights:
'Clearance expires ........... (time)' - this indicates that if the aircraft is not airborne by the time stated, a fresh clearance will need to be obtained;
'Take-off not before .......... (time)' - this is given so that the pilot can calculate the best time to start engines;
'Unable to clear ........ (level planned)' - when ATC is unable to clear the flight at the level planned an alternative will be offered whenever possible, the acceptance of which will avoid or reduce delay;
'Join Airways at .......... (place and level) not before .......... (time)' - may be used when an Airways clearance is given to an aircraft, the first part of whose flight from the origination aerodrome is in uncontrolled airspace.
1.6.1.3
Airborne Procedures (See also ENR 1.4, paragraph 2.1, Note 2)
1.6.1.3.1 When an aircraft is cleared to leave or join an Airway at a certain point, it should be flown so as to cross the actual boundary of the Airway as near to that point as is practicable.
1.6.1.3.2 All aircraft flying Airways are required to adhere to IFR procedures in all weather conditions. However, when radar cover is not available ATC may offer VMC climb or descent clearances in order to avoid excessive traffic delays. Such clearances will be offered subject to the following:
By day only in Visual Meteorological Conditions;
subject to the agreement of the pilot concerned;
the pilot will be responsible for effecting his own separation;
essential traffic information will be given;
1.6.1.3.3 Unless otherwise authorized by ATC, aircraft flying along Airways are required, in so far as practicable, to operate along the defined centre-line.
1.6.1.4
Flights Joining Airways
1.6.1.4.1 Pilots wishing to join an Airway are required to file a flight plan either before departure or when airborne, and to request joining clearance when at least 10 minutes flying time from the intended joining point. If the destination or any part of the route is subject to Air Traffic Flow Management, pilots must have received the required authorisation/approval from the appropriate Air Traffic Flow Management Unit (ENR 1.9).
1.6.1.4.2 Joining clearance should be obtained as follows: Initial call - '....... (identification) request joining clearance ....... (Airway) at ....... (position)'. When instructed by ATC the following flight details should be passed:
Identification;
Aircraft type;
Position and heading;
Level and flight conditions;
Departure aerodrome;
Estimated time at entry point;
Route and point of first intended landing;
True Airspeed;
Desired level on Airway (if different from the above).
1.6.1.4.3 Requests for joining clearance of Airways for which the Controlling Authorities are London or Scottish Control should be obtained as follows:
From the ATSU with which the aircraft is already in communication; or
from the appropriate FIR Controller (if different from (a)); or, if it is not possible to obtain any form of clearance using (a) or (b), then
on the published frequency of the Airway Controlling Authority.
1.6.1.4.4 In order to prevent confliction with other Airways traffic, pilots should ensure that they are at the cleared flight level when they cross the Airway boundary, unless specific permission to do otherwise has been given by ATC.
1.6.1.5
Flights Crossing Airways in IFR
1.6.1.5.1 Pilots wishing to cross an Airway are required to file a flight plan either before departure or when airborne, and to request crossing clearance when at least ten minutes flying time from the intended crossing point.
1.6.1.5.2 Crossing clearance should be obtained as follows: Initial call - '........ (identification) request crossing ........ (Airway) at ....... (position)'. When instructed by ATC the following flight details should be passed:
Identification;
Aircraft type;
Position and heading;
Level and flight conditions;
Position of crossing;
Requested crossing level;
Estimated time of crossing.
1.6.1.5.3 Requests for joining clearance of Airways for which the Controlling Authorities are London or Scottish Control should be obtained as follows:
From the ATSU with which the aircraft is already in communication; or
from the appropriate FIR Controller (if different from (a)); or, if it is not possible to obtain any form of clearance using (a) or (b), then
on the published frequency of the Airway Controlling Authority.
1.6.1.5.4 Unless otherwise requested by ATC, aircraft crossing Airways will remain in communication with the FIR Controller and, after obtaining clearance, will report as follows when the aircraft is estimated to be at the boundary of the Airway:
'.......... (identification) - Crossing .......... (Airway) .......... (position) .......... (time) .......... at .......... (level)'.
1.6.1.5.5 Except where otherwise authorized by ATC, aircraft are required to cross the Airway by the shortest route (normally, at right angles) and to be in level flight at the cleared flight level on entering the Airway.
1.6.1.6
Airway Crossings or Penetrations in VMC - Civil Aircraft
1.6.1.6.1
Powered Aircraft - Airway Crossings (See also ENR 1.4, paragraph 2.1, Note 2)
1.6.1.6.1.1 Powered aircraft may cross an Airway in VMC by day without compliance with the full IFR requirements in relation to the aircraft equipment provided that the pilot holds a valid Instrument Rating and that clearance is obtained from the appropriate ACC. This clearance must be obtained by RTF (normally on the FIR frequency); the request for clearance and a crossing report should be made as shown in paragraphs 1.4.1.5.3 and 1.4.1.5.5.
1.6.1.6.2
Powered Aircraft - Other penetrations of Airways (see also ENR 1.1, paragraph 4.1 and ENR 1.4, paragraph 2.1, Note 2).
1.6.1.6.2.1 Other flights in VMC, for example photographic survey flights, may also do so without compliance with full IFR requirements, provided that:
Prior arrangements are made with the appropriate ACC;
specific ATC clearance is obtained for individual flights;
the aircraft can communicate by RTF on the appropriate Airways frequency.
1.6.1.7
Procedures for Military Aircraft
1.6.1.7.1 These procedures apply to military aircraft in all weather conditions.
1.6.1.7.1.1 Military aircraft flying along Airways will conform to the normal Airways procedures.
1.6.1.7.1.2 Military aircraft crossing Airways will do so either:
Under the control of an approved Air Traffic Control Radar Unit; or
under a positive Air Traffic Control Clearance.
1.6.1.7.1.3 In an emergency, where neither a radar nor a procedural crossing can be obtained, an Airway may be crossed at an intermediate 500 FT level. The intermediate 500 FT levels referred to are flight levels of whole thousands plus 500 FT.
1.6.2
Air Traffic Advisory Routes
None are currently established by the UK.
1.6.3
The Upper Airspace Control Area
1.6.3.1
Rules. The following rules apply to aircraft flying in the Upper Airspace Control Area:
A flight plan must be filed; ATC permission must be obtained before the Area is entered; a continuous RTF watch must be kept on the appropriate frequency; the flight must be conducted in accordance with ATC instructions.
1.6.3.1.1 Altimeter Setting Procedures1.6.3.1.1.1 All aircraft flying in the Upper Airspace Control Area must use the standard altimeter setting of 1013.2 mb.
1.6.3.1.2 Cruising Levels1.6.3.1.2.1 Cruising levels will be allocated in accordance with the semi-circular rules depicted in the Table of Cruising Levels at ENR 1.7, paragraph 6. ATC may allocate a level not appropriate to the aircraft track, e.g. to effect transition to and from Oceanic levels.
1.6.3.1.2.2 The providers of Air Traffic Services in the United Kingdom Upper Airspace may apply a reduced vertical separation minimum of 1000 FT, between FL 290 and FL 410 inclusive, in the London and Scottish UIRs between aircraft that are RVSM approved. Aircraft that are not RVSM approved will be provided with a minimum of 2000 FT separation.
1.6.3.1.3 Exemptions1.6.3.1.3.1 By prior agreement, Research and Development flights may be exempted from some of the rules and procedures but ATC will co-ordinate such flights.
1.6.3.1.3.2 The above rules and procedures do not apply to gliders.
1.6.3.1.3.3 By prior agreement, civil aircraft operating on contract to the MoD, aircraft undergoing air tests, or aircraft calibrating navigation aids may be exempted from the RVSM requirements.
1.6.3.2
Co-ordination of Civil and Military Aircraft
1.6.3.2.1 NATS radars cover most of the Upper Airspace. Within this cover, procedures exist for the co-ordination of civil and known military aircraft and they receive a radar control and/or a procedural ATC Service. Outside radar cover, a procedural ATC service is provided.
1.6.3.2.2 Military aircraft are normally under the control of NATS or autonomous radar Units but outside the Mandatory Radar Service Area, they are not obliged to receive an ATC Service. In these circumstances it is not always possible for ATC to offer avoiding action because the behaviour of such aircraft is unpredictable. However, whenever practicable, ATC will pass traffic information on them to aircraft under control.
1.6.3.2.3 Due to the routine operation of high-speed military aircraft within the UIRs, civil aircraft operators should flight plan only on the published ATS Route Structure when operating outside the FRA volume as defined in ENR 2.2. When traffic conditions permit, ATC may authorize aircraft to fly more direct tracks. When planning through FRA, operators shall avoid active SUAs and associated FBZs and NPZs at their discretion unless specific routings are mandated: See ENR 1.10 Sect 3.
1.6.3.2.3.1 For individual flights within the Scottish UIR and outside the area defined for FRA operations, operators may file outside the published ATS Route Structure subject to authorisation by the Scottish ACC ATC Watch Manager (Tel: 01292-692763, Fax: 01292-692872). Authorisation for routine operations outside the published ATS Route Structure must be obtained from ATC Operational Support at Scottish ACC (Tel: 01292-692611, Fax: 01292 - 692610).
1.6.3.2.4 There is a military TACAN route system in the Upper Airspace. Some of the routes join the published Upper ATS Route Structure at certain reporting points as well as to a similar TACAN route network over the rest of Europe. See chart of the military TACAN routes at ENR 6-72.
1.6.3.3
Non-Standard Civil Flights and Unusual Aerial Activities in the UK Upper Airspace
1.6.3.3.1 Certain civil flying activities such as training and general test flying in Class C Airspace above FL 195 may require a specialized radar service that can best be provided by military ATS Units. However, it should be borne in mind that the aircraft handling capacity of military ATS Units may be committed to the Units primary tasks, and therefore, it is advisable that aircraft operators requiring a service should discuss their proposed task with the relevant ATS Unit prior to commencement of the flight.
1.6.3.3.2 Information concerning the military ATS Units may be obtained from the RAF en-route documents or from civil ATS Units.
1.6.3.3.3 The approval of an Unusual Aerial Activity (UAA) in Class C Airspace above FL 195 can often only be given after extensive co-ordination and the request should be submitted at the earliest opportunity to Airspace Regulation (Utilisation) (AR(U)), Airspace Regulation, Aviation House, Gatwick RH6 0YR, as detailed at ENR 1.1, paragraph 4.3.
1.6.3.4
Flight Plans, ATC clearance and other procedures
The normal requirements for flight plans, ATC clearance, and the regulations, rules and procedures appropriate for flight in Control Areas apply.
1.6.3.4.1
Night Time Fuel Saving Routes
1.6.3.4.1.1 Night Time Fuel Saving Routes (NTFSR) are introduced in UK upper airspace, excluding airspace defined as FRA, and are routes that formalise the practice of giving flight plannable direct routings (DCT) to GAT at set times overnight. NTFSR will enable the proportion of flights flying direct to increase during their hours of operation and will thereby produce a reduction in CO2 emissions. Details of the routes will be included in Appendix 4 of the UK RAD.
1.6.3.4.2
Loss of Communication
1.6.3.4.2.1 In the event of radio communication failure, pilots will follow the procedures shown at ENR 1.1, paragraph 3.4. Attempts should also be made to establish communication on other control channels available in the Scottish FIR/UIR or on NARTEL HF channels.
1.6.3.5
Military Training Areas (MTA)
1.6.3.5.1 MTAs are established in the UK for the operational freedom of military aircraft engaged in exercise or training, and the nature of this activity is incompatible with civil air traffic services procedures. Civil pilots should not therefore flight plan any route through active MTAs nor make in-flight requests for transit through these areas when they are active as ATC cannot authorise such flights. However, for the following categories of civil registered aircraft, an ATS may be available within an active MTA from the appropriate military air traffic control radar unit:
Aircraft in emergency which may have to be routed through an active MTA for flight safety reasons;
aircraft sponsored by DE&S;
test flights by UK manufacturers of military and civilian aircraft;
airtests by civil or military aircraft departing from or arriving at UK aerodromes;
special flights authorised by HQ AIR (ATM Force);
air ambulance flights, where the most expeditious routing is justifiable on humanitarian grounds.
Note 1: Pilots of such aircraft requiring this service should make their request to the UK Civil ATS Unit or Military Unit with which they are in contact.
Note 2: Military controllers may provide aircraft in the above categories with UK Flight Information Services (UK FIS) (radar services detailed in ENR 1.6, paragraph 1.3) and pilots are to ensure that they are familiar with the types of services available.
1.6.3.5.2 If pilots inadvertently flight plan to transit MTAs during notified periods of activity, ATS instructions will be issued to re-route the aircraft around those areas. To avoid such unexpected routing, pilots are requested to ensure that account is taken of the published periods of activity of any MTA near the route (detailed in ENR 5.2), when planning their flight.
1.6.3.5.3 MTAs are depicted on the charts at ENR 6-70 and ENR 6-75.
1.6.3.6
North Sea Reduced Co-Ordination Area
1.6.3.6.1 The North Sea Reduced Co-ordination Area (RCA) has been established within UK Upper Airspace to optimise airspace availability as a result of tactical handbacks of any portion of the EGD323 complex. As a result, direct point to point routings may be offered when airspace structures permit that would not normally allow the availability of a published CDR. The co-ordination requirements between OAT and GAT follow those set out within CAP 1430 and the Eurocontrol Airspace Management Handbook which are detailed within an LOA between the MOD and NATS.
1.6.3.6.2 Description of lateral and vertical dimension of the North Sea RCA are contained within ENR 2.2 and depicted in ENR 6.
1.6.3.7
FRA Reduced Co-Ordination Area
1.6.3.7.1 The FRA Reduced Co-ordination Area (RCA) has been established within UK upper airspace. The lateral and vertical dimension of the FRA RCA match that of the EGPX FRA area and are contained within ENR 2.2 and depicted in ENR 6-70.
1.7 Reporting Points
1.7.1 Compulsory Reporting Points are marked with a ▲. Reporting Points marked with a ∆ are 'on request' Reporting Points, at which a report will be made only when requested by the controlling authority.
1.8 Terrain Clearance
1.8.1
Control Areas (Airways)
1.8.1.1 Where the lower limit of a section of an Airway is defined as a Flight Level and therefore varies in height, an absolute minimum altitude applies. This minimum altitude for the Airway base is at least 1000 FT above any fixed obstacle within 15 NM of the centre-line. The lowest usable level will always be at least 500 FT above the Airway base, thus providing not less than 1500 FT terrain clearance within 15 NM of any position on the centre-line of the Airway.
1.8.1.2 On sections of Airways adjacent to Control Zones and Areas where the lower limit is established at not less than 700 FT above terrain, ATC clearances are designed to enable aircraft to remain at least 500 FT above the base of the Airway.
1.9 En-Route Holding
1.9.1
Control Areas (Airways)
1.9.1.1 Except where otherwise instructed by ATC, holding en-route will be carried out on tracks parallel to the centre-line of the Airway, turning right at the Reporting Point. Exceptions are shown at ENR 3.6.
1.9.1.2 Whenever possible, pilots will be given a specific time at which to leave the Reporting Point and the holding pattern should be adjusted accordingly.
1.9.1.3 Pilots are required to report as follows:
The time and level of reaching a specific holding point to which cleared;
when leaving a holding point;
when vacating a previously assigned level for a new assigned level.
1.9.2
En-Route High Level Holding
1.9.2.1 Within the Upper Airspace, en-route holding patterns have been established. The 1.5 minute holding patterns, based on ICAO recommended speeds, are as shown at ENR 3.6.
1.10 Hazards and Danger Areas
1.10.1
The Upper Airspace Control Area
1.10.1.1 The Chart of the United Kingdom Airspace Restrictions at ENR 6-75 (as amended), NOTAM and AICs should always be consulted for information on activity in Danger Areas adjacent to the route being flown.
1.11 Glider Operations above FL 195
1.11.1 The paragraphs below set out the procedures for glider operations above FL 195 within the following airspace structures:
Temporary Reserved Area (Gliding) (TRA (G)) in Class C Airspace between FL 195 - FL 240 (ENR 5-2-4/7);
Temporary Reserved Area (Gliding) (TRA (G)) in Class C Airspace above FL 240 (ENR 5-2-4/7);
Temporary Reserved Area (TRA) in Class C Airspace between FL 195 and FL 245 (ENR 5-2-2/3);
Class C Airspace outside TRA and TRA (G) between FL 195 - FL 285.
1.11.2 Glider operations above FL 195 are to be conducted only in accordance with the following criteria:
1.11.2.1 VFR criteria:
Level | Distance from Cloud | Flight Visibility |
|---|
At and above FL 195 | 1500 M Horizontally 1000 FT Vertically | 8 KM |
1.11.2.2 Operations shall be in accordance with a Letter of Agreement (LoA), or specific permission.
1.11.2.3 Operations shall be conducted on the SPS (1013.2 mb).
1.11.2.4 Radio contact must be maintained on the appropriate frequency.
Note: Radio frequency requirements for VFR operations by gliders above FL 195 within a Temporary Reserved Area (TRA), Temporary Reserved Area (Gliding) (TRA (G)) or for a specified VFR permission outside a TRA, will be detailed in the respective TRA Letter of Agreement (LoA), or specific permission.
1.11.3
Procedures for non-SSR equipped Glider Operations within Temporary Reserved Area (Gliding) (TRA (G)) in Class C Airspace between FL 195 - FL 240
1.11.3.1 TRA (G) have been provided to accommodate non-SSR equipped gliders. (See ENR 5.2, ENR 6-64 and ENR 6-65).
1.11.3.2 Gliders equipped with SSR transponders should squawk 7006 whilst operating in the TRA (G).
1.11.3.3
Glider Operations in TRA (G) between FL 195 - FL 240 must comply with the following requirements:
-
Each TRA (G) shall have a nominated gliding club(s) to manage booking arrangements with the appropriate ACC.
-
The nominated gliding club(s) will request booking of the required TRA (G) airspace 2 hours in advance on the day of operation.
-
A requested upper flight level shall be specified at the time of booking.
-
ACC civil and military supervisors shall co-ordinate booking request and agree initial access arrangements based on the prevailing and forecast GAT/OAT traffic situation.
-
A request to activate the TRA (G) shall be made only when the club(s) have positively established that access is required. No glider will enter until a positive ATC clearance has been obtained to enter the TRA (G). This may be either by telephone or RTF contact with the ACC.
-
Gliders shall monitor the appropriate gliding frequency specified in the LoA whilst operating within the TRA (G).
-
Gliders shall remain within the lateral boundaries of the TRA (G) and below the agreed upper flight level.
-
The gliding club(s) shall provide a contact telephone number to enable the parent ACC to close the TRA (G); if such a request is received the nominated gliding club(s) will direct gliders to vacate the TRA (G) as expeditiously as possible.
-
The nominated gliding club(s) will notify the ACC that TRA (G) activity is complete.
-
Additional requirements and detailed contact arrangements will be contained in a LoA between the responsible ACC and nominated gliding club.
1.11.4
Procedures for non-SSR equipped Glider Operations within Temporary Reserved Area (Gliding) (TRA (G)) in Class C Airspace above FL 240
1.11.4.1 All non-SSR equipped glider operations above FL 240 must be conducted in TRA (G).
1.11.4.2 The gliding representative will initiate a request to the appropriate area control supervisor (see paragraph 9.4.3) 2 hours in advance of the intended flight advising the intention to use the designated area and confirm the following details:
Temporary Reserved Areas concerned (See ENR 5.2, ENR 6-66 and ENR 6-67);
Requested upper limit (Scottish Upper Area (North) has an upper limit of FL 270);
Expected time of entry into, and duration in the Upper TRA (G) (negotiated if any other priority ACC task);
The number of gliders and associated callsign(s);
Name and telephone contact number.
1.11.4.3 Area Control contact telephone numbers:
For Scottish, Spadeadam, Yorkshire and Northern Ireland areas, contact Scottish ACC, Civil ATC Watch Supervisor (WS) on Tel: 01292-692763.
For Welsh areas, contact Swanwick Military Supervisor (SMS) on Tel: 01489-612417.
1.11.4.4 Following notification, the Supervisor will contact the gliding representative to discuss the activity, and allocate the frequency to be employed, or, if the activity cannot be accommodated, advise the representative of the reason and negotiate a new period.
1.11.4.5 The glider pilot shall establish 2-way RTF contact passing FL 200 in the climb, obtain an ATC clearance to enter the TRA ( G), maintain a listening watch on the frequency, and report again when passing FL 240 in descent.
1.11.4.6 The military controller will initiate a radio check with the glider pilot on the hour and half hour whilst the aircraft is above FL 240 to confirm continuing RTF contact. In the event of not receiving a radio check call the glider pilot will immediately attempt to re-establish 2-way contact and if unsuccessful shall descend below FL 240 within 15 minutes.
Note: 15 minutes after the last unsuccessful ‘operations normal’ radio check by the military controller the airspace above FL 240 will be deemed clear of gliders and GAT aircraft will be allowed access.
1.11.4.7 The glider pilot is responsible for remaining within the designated area. In addition, all gliders flying within TRA (G) above FL 240 are to be fitted with appropriate radio and navigational equipment. In the event of either of these equipments becoming unserviceable, gliders are to descend below FL 240.
1.11.4.8 Whilst operating within a designated area, glider pilots will be in receipt of a Flight Information Service with proximity warnings of either aircraft in emergency or Air Defence Flights, which need to transit the area. The glider pilots will be responsible for their own separation.
1.11.4.9 Whilst operating within a designated TRA (G) above FL 240, all position reports are to be made in relation to Airway/Upper ATS Route Reporting Points.
1.11.4.10 Additional requirements and detailed contact arrangements will be contained in a LoA between the responsible ACC and nominated gliding club(s).
1.11.5
Procedures for SSR equipped Glider Operations within Temporary Reserved Area (TRA) in Class C Airspace between FL 195 - FL 245
1.11.5.1 Gliders equipped with RTF and SSR transponder may operate in accordance with VFR within Temporary Reserved Areas (TRA) in Class C Airspace between FL 195 and FL 245 provided that the pilot:
Files a flight plan (when specified an abbreviated flight plan will be acceptable).
Obtains an ATC clearance to enter the TRA (See ENR 5.2 and ENR 6-13).
Monitors ATC frequency.
Selects SSR Code A/C as directed by ATC.
Whilst operating within a designated area, glider pilots will be in receipt of a Flight Information Service.
1.11.5.2 Detailed access requirements to TRA will be detailed in the LoA between the ACC responsible for the airspace and the nominated gliding club(s) concerned.
1.11.6
Procedures for Glider Operations in Class C Airspace outside TRA and TRA (G) between FL 195 - FL 285
1.11.6.1 Glider operations in Class C Airspace between FL 195 - FL 285 must comply with the following requirements:
The flight must be conducted in accordance with ATC instructions and/or conditions specified in LoAs or specific permission.
A flight plan must be filed. Where specified an Abbreviated Flight Plan will be acceptable as detailed in the LoA between the ACC responsible for the airspace and the nominated gliding club(s) concerned.
An ATC clearance must be obtained to fly within the airspace.
Select SSR Code A/C as directed by ATC.
Maintain listening watch on the ATC frequency.
In the event that 2-way RTF contact is lost, pilots shall squawk 7600 and descend below controlled airspace (FL 195) as expeditiously as possible.
1.11.6.2 Other Gliding Activity
1.11.6.2.1 Gliding clubs seeking access to airspace above FL 195 to facilitate special events should contact AUS in accordance with procedures detailed at ENR 1.1, paragraph 4.1.9.
1.12 Procedures for Non-SSR Transponder equipped Glider Operations at and above FL 100 up to FL 195
1.12.1 Non-SSR Glider Areas have been established to accommodate non-transponder equipped glider operations at and above FL 100 up to FL 195 (See ENR 5.2 and ENR 6-63).
1.12.2 ATC clearance is required prior to access of that Class A, C and D Airspace lying within Non-SSR Glider Areas.
1.12.3 Other than that portion of airspace notified as Class A, C and D Airspace the background airspace classification of Non-SSR Glider Areas is Class G, with UK FIS provided on request, where available; and in accordance with ENR 1.1 and ENR 1.6.
1.12.4 The glider pilot is responsible for remaining within the designated area.
2 UK Flight Information Services
2.1 Overview
2.1.1 The ICAO requirements for a Flight Information and Alerting Service are met in the Scottish FIR/UIR and the London FIR/UIR through a suite of services, collectively known as the UK Flight Information Services (FIS), and are provided through the following provisions:
To participating flights arriving at, departing from and overflying aerodromes located within Class G Airspace as listed at GEN 3.3.
To participating VFR flights operating within Class E Airspace, as listed at ENR 3.1.
To aircraft within Advisory Radio Areas as listed at ENR 1.1, paragraphs 5.2.5/6 and ENR 5.2.
Lower Airspace Radar Services (LARS) and Radar Service - FL 100 and above (outside CAS), as listed at ENR 1.6.
Area Control Centre (ACC) services, including the provision of service by ACC FISOs as detailed at GEN 3.3.
2.1.2 The UK FIS (Basic Service, Traffic Service, Deconfliction Service, Procedural Service) are detailed herein. Within the UK, the scope of FIS, as defined in ICAO Annex 11, is met through the provision of a Basic Service.
2.2 Service Principles
2.2.1 Within Class G Airspace, regardless of the service being provided, pilots are ultimately responsible for collision avoidance and terrain clearance, and they should consider service provision to be constrained by the unpredictable nature of this environment.
2.2.2 A pilot shall determine the appropriate service for the various phases and conditions of flight and request that service from the controller/FISO; a Deconfliction Service and Procedural Service shall only be provided to flights under IFR, irrespective of meteorological conditions. An Alerting Service will be provided in association with all services.
2.2.3 Controllers will make all reasonable endeavours to provide the service that a pilot requests. However, due to finite resources or controller workload, tactical priorities may influence service availability. FISOs are not licensed to provide Traffic Service, Deconfliction Service, or Procedural Service.
2.2.4 Instructions issued by controllers/FISOs to pilots operating outside controlled airspace are not mandatory; however, the services rely upon pilot compliance with the specified terms and conditions so as to promote a safer operating environment for all airspace users.
2.2.5 Agreements can be established between a controller and a pilot such that the operation of an aircraft is laterally or vertically restricted beyond the core terms of the Basic Service or Traffic Service. Unless safety is likely to be compromised, a pilot shall not deviate from an agreement without first advising and obtaining a response from the controller.
2.2.6 There may be circumstances that prevent controllers/FISOs from passing timely traffic information and/or deconfliction advice, eg high workload, areas of high traffic density, against unknown aircraft conducting high energy manoeuvres, or when traffic is not displayed to the controller or obscured by surveillance clutter. Controllers/FISOs shall inform the pilot of known reductions in traffic information along with the reason and the probable duration; however, it may not always be possible to provide these warnings in a timely fashion.
2.3 Basic Service
2.3.1 Basic Service provides advice and information useful for the safe and efficient conduct of flights. This may include weather information, changes of serviceability of facilities, conditions at aerodromes, general airspace activity information, and any other information likely to affect safety. The avoidance of other traffic is solely the pilot's responsibility.
2.3.2 Basic Service is available under IFR outside controlled airspace in any meteorological conditions, or under VFR.
2.3.3 Pilots should not expect any form of traffic information from a controller/FISO and the pilot remains responsible for collision avoidance at all times. However, where a controller/FISO has information that indicates that there is aerial activity in a particular location that may affect a flight, they should provide traffic information in general terms to assist with the pilot's situational awareness. This will not normally be updated by the controller/FISO unless the situation has changed markedly, or the pilot requests an update.
2.3.4 Basic Service is available at all levels and the pilot remains responsible for terrain clearance at all times.
2.3.5 Unless the pilot has entered into an agreement with a controller to maintain a specific course of action, a pilot may change heading, route, or level without advising the controller. A controller will not issue specific heading instructions; however, generic navigational assistance may be provided on request.
2.4 Traffic Service
2.4.1 Traffic Service is a surveillance based ATS, where in addition to the provisions of a Basic Service, the controller provides specific surveillance derived traffic information to assist the pilot in avoiding other traffic. The avoidance of other traffic is solely the pilot's responsibility.
2.4.2 Traffic Service is available under IFR outside controlled airspace in any meteorological conditions, or under VFR. If a controller issues a heading and/or level that would require flight in IMC, a pilot who is not suitably qualified to fly in IMC shall inform the controller and request alternative instructions.
2.4.3 The controller will pass traffic information on relevant traffic, and update the traffic information if it continues to constitute a definite hazard, or if requested by the pilot. However, high controller workload and RTF loading may reduce the ability of the controller to pass traffic information, and the timeliness of such information. Whether traffic information has been passed or not, a pilot is expected to discharge his collision avoidance responsibility without assistance from the controller. Whilst operating in Class G Airspace, if after receiving traffic information a pilot requires deconfliction advice, an upgrade to Deconfliction Service shall be requested. Deconfliction Service is not available in Class E Airspace.
2.4.4 Subject to ATS surveillance system coverage, Traffic Service may be provided at any level and the pilot remains responsible for terrain clearance at all times.
2.4.5 A pilot may operate under their own navigation and may select their own operating levels, or a controller may provide headings and levels for the purpose of positioning, sequencing or as navigational assistance. If a heading or level is unacceptable to the pilot they shall advise the controller immediately.
2.4.6 When operating under their own navigation, pilots may alter course as required; however, unless safety is likely to be compromised, pilots shall not change their general route or manoeuvring area without first advising and obtaining a response from the controller.
2.4.7 When following an ATC heading, unless safety is likely to be compromised, a pilot shall not change heading without first advising and obtaining a response from the controller.
2.4.8 Unless safety is likely to be compromised, a pilot shall not change level or level band without first advising and obtaining a response from the controller.
2.5 Deconfliction Service
2.5.1 A Deconfliction Service is a surveillance based ATS where, in addition to the provisions of a Basic Service, the controller provides specific surveillance derived traffic information and deconfliction advice.
2.5.2 A Deconfliction Service shall only be provided to flights under IFR in Class G Airspace, irrespective of meteorological conditions. The controller will expect the pilot to accept headings and/or levels that may require flight in IMC. A pilot who is not suitably qualified to fly in IMC shall not request a Deconfliction Service unless compliance permits the flight to be continued in VMC.
2.5.3 A controller will provide traffic information, accompanied with a heading and/or level aimed at achieving a planned deconfliction minima. High controller workload or RTF loading may reduce the ability of the controller to pass such deconfliction advice; furthermore, unknown aircraft may make unpredictable or high-energy manoeuvres. Consequently, controllers cannot guarantee to achieve these deconfliction minima; however, they shall apply all reasonable endeavors. The avoidance of traffic is ultimately the pilot's responsibility.
2.5.4 The pilot shall inform the controller if he elects not to act on the controller's deconfliction advice, and therefore accepts responsibility for initiating any subsequent collision avoidance against that particular conflicting aircraft.
2.5.5 A Deconfliction Service will only be provided to aircraft operating at or above a terrain safe level, unless on departure from an aerodrome when climbing to a terrain safe level, or when following notified instrument approach procedures. If a controller detects a confliction when an aircraft is departing from an aerodrome and climbing to the terrain safe level, or when following notified instrument approach procedures, traffic information without deconfliction advice shall be passed. However, if the pilot requests deconfliction advice, or the controller considers that a definite risk of collision exists, the controller shall immediately offer such advice.
2.5.6 Unless safety is likely to be compromised, a pilot shall not change heading or level without first obtaining approval from the controller.
2.6 Procedural Service
2.6.1 A Procedural Service is a non surveillance ATS where, in addition to the provisions of a Basic Service, the controller provides instructions, which if complied with, shall achieve deconfliction minima against other aircraft participating in the Procedural Service. Neither traffic information nor deconfliction advice can be passed with respect to unknown traffic.
2.6.2 A Procedural Service shall only be provided to flights under IFR, irrespective of meteorological conditions. The controller will expect the pilot to accept levels, radials, tracks, routes and time allocations that may require flight in IMC. A pilot who is not suitably qualified to fly in IMC shall not request a Procedural Service unless compliance permits the flight to be continued in VMC.
2.6.3 A Procedural Service is available at all levels and the pilot remains wholly responsible for terrain clearance at all times.
2.6.4 A controller will provide deconfliction instructions by allocating levels, radials, tracks, routes, time restrictions, approach clearances and holding instructions, or use pilot position reports, aimed at achieving a planned deconfliction minima. The pilot shall inform the controller if they elect not to act on the controller's deconfliction advice, and therefore accepts responsibility for initiating any subsequent collision avoidance against the aircraft in question and any other aircraft affected.
2.6.5 The controller will provide traffic information on conflicting aircraft being provided with a Basic Service and those where traffic information has been passed by another ATS unit; however, there is no requirement for deconfliction advice to be passed, and the pilot is wholly responsible for collision avoidance.
2.6.6 Unless safety is likely to be compromised, a pilot shall not change level, radial, track, route or time restriction without first obtaining approval from the controller. If a level, radial, track, route or time restriction is unacceptable to the pilot, they shall advise the controller immediately.
3 General Flight Procedures
3.1 Position Reporting within the London and Scottish FIR/UIR
3.1.1 Pilots are to make a position report in the following circumstances:
After transfer of communication;
on reaching the limit of ATS clearance;
when instructed by Air Traffic Control;
when operating helicopters in the North Sea Low Level Radar Advisory and Flight Information areas of responsibility and on Helicopter Routes within the London Control Zone and London/City Control Zone (see ENR 1.6, subsection 4.5 and AD 2.EGLL 2.22, paragraph 11);
when operating flights across the English Channel (see ENR 1.1, paragraph 3.7).
3.1.1.1 The initial call changing radio frequency shall contain only the aircraft identification and flight level. Any subsequent report shall contain aircraft identification, position and time except as provided for in respect of helicopter operations in the areas specified in paragraph 3.1.1 (d) above.
Note: When changing frequency between the London or Scottish Control Centres, pilots are required to state their callsign and Flight Level/Altitudes only (plus any other details when specifically instructed by ATC). When the aircraft is in level flight but cleared to another FL/ALT, both FL/ALT should be passed. Similarly, when the aircraft is not in level flight, the pilot should state the aircraft identification followed by the FL/ALT to which it is cleared only; it is not necessary to state passing FL/ALT in these circumstances.
3.1.1.2 Certain Reporting Points on the boundary between the London FIR/UIR and the Amsterdam FIR are designated 'Compulsory' in the Netherlands AIP. Position Reports should therefore be made at these points when in communication with Amsterdam or Maastricht Control.
3.1.2
Omit Position Report Procedure
3.1.2.1 In order to reduce RTF communication a pilot may be instructed by Air Traffic Control to omit position reports provided that the aircraft is radar identified.
3.1.3
DME Distance Reports to ATC
3.1.3.1 Pilots, when requested by ATC to report their distance from a DME facility which they do not have displayed, should retune their equipment to that DME. If, for any reason, they are unable to report their distance from the requested DME, ATC is to be informed. Pilots should not calculate the distance based on the reading from another DME.
3.2 Climb and Descent
3.2.1
Vacating (Leaving) Levels
3.2.1.1 When pilots are instructed to report leaving a level, they should advise ATC that they have left an assigned level only when the aircraft's altimeter indicates that the aircraft has actually departed from that level and is maintaining a positive rate of climb or descent in accordance with published procedures.
3.2.2
Level Restrictions
3.2.2.1 For all stages of flight, clearances to climb or descend cancel any previous restrictions or levels, unless they are reiterated as part of the clearance.
3.2.2.2 When a departing aircraft on a SID is required to climb directly to the cleared level without complying with the published vertical restrictions on the SID, ATC will include the word ‘now’ in climb instructions (e.g. Jet 347 climb now FL 120).
3.2.2.3
Maximum Rates of Climb and Descent
3.2.2.3.1 In order to ensure the credible interaction of Airborne Collision Avoidance Systems and ground based safety nets, other than aircraft in emergency and certain specific conditions for military aircraft (as detailed in Military AIP and MAA Regulatory Publication RA 3000 Series), all aircraft when operating under normal circumstances, when inside Controlled Airspace within the London and Scottish FIRs/UIRs should not operate with a climb or descent rate exceeding 8000 FT per minute. Aircraft when first approaching a cleared flight level and/or when changing flight level in Controlled Airspace should ensure that the vertical closure speed is not excessive. It is considered that, with about 1500 FT to go to a cleared level, vertical speed should be reduced to a maximum of 1500 FT per minute and ideally to between 1000 FT per minute and 500 FT per minute. Pilots should ensure that the aircraft neither undershoots nor overshoots the cleared level by more than 150 FT, manually overriding if necessary.
3.2.2.4
Minimum Rates of Climb and Descent
3.2.2.4.1 In order to ensure that controllers can accurately predict flight profiles to maintain standard vertical separation between aircraft, pilots of aircraft commencing a climb or descent in accordance with an ATC Clearance should inform the controller if they anticipate that their rate of climb or descent during the level change will be less than 500 FT per minute, or if at any time during such a climb or descent their vertical speed is, in fact, less than 500 FT per minute.
3.2.2.4.2 This requirement applies to both the en-route phase of flight and to terminal holding above Transition Altitude.
Note: This is not a prohibition on the use of rates of climb or descent of less than 500 FT per minute where necessary to comply with other operating requirements.
3.2.2.5
Noise Abatement Approach Techniques
3.2.2.5.1 The use of Continuous Descent Approach (CDA) and Low Power/Low Drag Approach (LP/LD) techniques (as defined at GEN 2.2) is required, subject to compliance with ATC requirements, at certain UK Airports as detailed in the appropriate AD 2 Sections. At other locations, although not required, these techniques are considered to be ‘best practice’ for the reduction of noise nuisance and emissions and should be adopted by pilots whenever operationally practicable, commensurate with the ATC clearance.
3.3 Speed Control
3.3.1 Pilots shall adhere to the speed limits associated with airspace classifications and the speed restrictions notified in procedures published in AD 2. Pilots shall also adhere to the speed (IAS or Mach Number) approved or assigned by ATC and shall request ATC approval before making any changes thereto. If it is essential to make an immediate temporary change in speed (e.g. due to turbulence), ATC shall be notified as soon as possible that such a change has been made.
3.3.2 Pilots of aircraft unable to maintain the last assigned speed during any particular phase of flight (eg for aircraft performance reasons) shall inform ATC as soon as possible in order that another speed/alternative clearance can be issued.
3.3.3 At levels at or above FL 280, speed adjustments for aircraft in the cruise will be expressed in multiples of 0.01 Mach. At levels below FL 280, speed adjustments will be expressed in multiples of 10 KT based on indicated airspeed (IAS).
3.3.4 For aircraft at or above FL 280 that have been cleared to descend to levels below FL 280, speed adjustments may be based on IAS.
3.4 Radiotelephony, Radio Failure and Loss of Communication Procedures
3.4.1
General Radiotelephony Procedures
3.4.1.1 The English Language is used for all communications between aircraft and ATC in the UK.
3.4.1.2 VHF/RTF is used for all air-ground communications throughout the airspace under UK jurisdiction except that HF is also used in the Shanwick Oceanic Control Area and that UHF is also available at London Area Control (Swanwick) and at certain aerodromes (see ENR 1.6, subsection 4.5 and ENR 2.1 sections for details).
3.4.1.3 So far as possible, pilots should make use of the ICAO standard RTF phraseology in ICAO Doc. 4444, Chapter 12 when communicating with ATC. UK specific differences to ICAO phraseology are notified in GEN 1.7 section.
3.4.1.3.1 As a general principle all messages should be acknowledged by use of the aircraft callsign or ‘Roger, (callsign)’.
3.4.1.3.2 Messages containing any of the following items must be read back in full:
Taxi/towing instructions;
Level instructions;
Heading instructions;
Speed instructions;
Airways or route clearances;
Approach clearances;
Runway-in-use;
Clearance to enter, land on, take-off, backtrack or cross or hold short of an active runway;
SSR operating instructions;
Altimeter Settings, including units when value is below 1000 hectopascals;
VDF information;
Frequency changes;
Type of ATS surveillance service;
Transition level.
3.4.1.3.3 When an estimate for a compulsory or non-compulsory reporting point, flight information boundary, or destination aerodrome is requested by an ATS unit and is in error by in excess of 2 minutes, pilots are required to provide a revised estimate to an appropriate ATS unit as soon as possible.
3.4.1.3.4 Where data link communications are used to facilitate clearance delivery, voice read-back of data link messages shall not be required unless otherwise notified by the appropriate authority.
3.4.1.4
Operations Normal
3.4.1.4.1 Pilot transmissions containing the RTF phraseology 'operations normal' are generally associated with aerial activities over mountainous or sparsely populated areas (including sea areas), where the flight receiving an ATS is required to operate within the area of responsibility of a single ATSU for prolonged periods of time. Such transmissions are made by pilots following a period of RT inactivity of 30 minutes.
3.4.1.4.2 The pilot’s declaration of 'operations normal' is used to inform the ATSU that the flight is progressing according to plan. Controllers who do not receive an 'operations normal' report when expected will attempt to establish communications with the pilot. After three failed attempts, controllers will initiate overdue action.
3.4.2
Radio Failure Procedures For Pilots
3.4.2.1
Failure of Navigation Equipment
3.4.2.1.1 If part of an aircraft’s radio navigation equipment fails but two-way communication can still be maintained with ATC, the pilot must inform ATC of the failure and report his altitude and approximate position. ATC may, at its discretion, authorize the pilot to continue his flight in or into Controlled Airspace. When radar is available it may, subject to workload, be used to provide navigational assistance to the pilot.
3.4.2.1.2 If no authorization to proceed is given by ATC, the pilot should leave, or avoid Controlled Airspace and areas of dense traffic, and either:
Go to an area in which he can continue his flight in VMC or (if this is not possible);
select a suitable area in which to descend through cloud, fly visually to a suitable aerodrome and land as soon as practicable.
But before doing so, however, he should consult ATC who may be able to give him instructions or advice. He should also take into consideration the latest meteorological information and terrain clearance and should make full use of ground VHF DF stations. He must at all times keep ATC informed of his intentions.
3.4.2.2
Failure of Two-way Radio Communications Equipment
3.4.2.2.1 As soon as ATC know that two-way communication has failed they will, as far as practical, maintain separation between the aircraft experiencing the communication failure and other aircraft, based on the assumption that the aircraft will operate in accordance with radio communication failure procedures described below.
3.4.2.2.2 Flight crews should note that air traffic control might not be aware of the loss of communications, so should not anticipate that appropriate measures to facilitate a landing have been implemented. Flight crews intending to land should therefore be alert to the possibility that vehicles, personnel and or other traffic may be occupying or entering the runway.
3.4.2.2.3 It should be noted that for many aerodromes in the UK, the radio communications failure procedures published in the AD 2 section differ from, or amplify, the basic procedures published below.
3.4.2.2.4
For the purposes of these procedures, ATC will expect an IFR flight following the ATS route structure to adopt the IMC procedure in paragraph 3.4.2.4. If there is an overriding safety reason, the pilot may adopt the VMC procedure.
3.4.2.2.5 Flights operating outside controlled airspace, without reference to ATS, should only use these procedures when the pilot decides that there is a need to alert ATC that two-way radio communications failure has occurred.
3.4.2.2.6 It should be noted that the use of loss of two-way communications procedures may result in aircraft flying outside controlled airspace.
3.4.2.2.7 The procedures detailed in this section apply to two-way radio communications failure. In the event that an additional emergency situation develops, ATC will expect the pilot to select secondary radar transponder on Mode A, Code 7700.
3.4.2.2.8 The expression Expected Approach Time (EAT) will mean either an EAT given by the appropriate ATC Unit or, if the pilot has been given 'No delay expected', the ETA over the appropriate designated landing aid serving the destination aerodrome.
3.4.2.2.9 Pilots are given an EAT of 'Delay not determined' when the destination runways cannot be used for landing and it is not possible to accurately predict when they will become available. In some circumstances an EAT of 'Delay not determined' will also be given when a preceding flight has elected to remain over the holding facility pending an improvement in weather conditions at the destination. If 'Delay not determined' has been given, do not attempt to land at the destination aerodrome, divert to the alternate destination specified in the current flight plan or another suitable airfield.
3.4.2.2.10 The 'current flight plan' is the flight plan, as filed and acknowledged with an ATC Unit, by the pilot or a designated representative.
3.4.2.2.11 The procedure that should be used by Special VFR Flights is detailed at ENR 1.2, paragraph 2.9.
3.4.2.2.12 Essential information may be relayed by ATC using the ACARS/Data Link. Pilots may endeavour to use alternative methods for communicating with ATC such as HF. The Distress and Diversion Cell (D&D) serving the London FIR/UIR and the Scottish FIR/UIR may be contacted by phone by aircraft that have approved installations that can access the UK telephone network. The telephone number is:
3.4.2.3
Visual Meteorological Conditions (VMC)
3.4.2.3.1 A VFR flight experiencing communication failure shall:
When VMC can be maintained, the pilot should set transponder on Mode A, Code 7600 with Mode C and land at the nearest suitable aerodrome. Pilots should take account of visual landing aids and keep watch for instructions as may be issued by visual signals from the ground. The pilot should report arrival to the appropriate ATC unit as soon as possible. When VMC cannot be maintained, the pilot should adopt the procedures for IMC detailed below.
3.4.2.3.2 Subject to the provisions of paragraph 3.4.2.2.3, an IFR flight experiencing communication failure in VMC shall:
When VMC can be maintained, the pilot should set transponder to Mode A, Code 7600 with Mode C and land at the nearest suitable aerodrome. Pilots should take account of visual landing aids and keep watch for instructions as may be issued by visual signals from the ground. The pilot should report arrival to the appropriate ATC unit as soon as possible. If it does not appear feasible to continue the flight in VMC, or if it would be inappropriate to follow this procedure, the pilot should adopt the procedures for flights in IMC detailed below.
Note: Pilots already in receipt of an ATC clearance may enter controlled airspace and follow the procedures referred to above. Those flights, that have not received an ATC clearance, should not enter controlled airspace unless an overriding safety reason compels entry.
3.4.2.4
Instrument Meteorological Conditions (IMC)
3.4.2.4.1 A flight experiencing communications failure in IMC during an approach directed by radar shall:
Operate secondary radar transponder on Mode A code 7600 with Mode C.
Continue either visually, or by means of promulgated Initial Approach Procedures and an appropriate approved final approach aid, to land. If this is not practical, carry out the missed approach procedure and continue to a holding facility appropriate to the airfield of intended landing for which an instrument approach is notified and then carry out that procedure.
3.4.2.4.2 Except where communications failure occurs during an approach directed by radar, a flight experiencing communication failure in IMC shall:
Operate secondary radar transponder on Mode A code 7600 with Mode C.
Maintain for a period of seven minutes, the current speed and last assigned level or minimum safe altitude, if this is higher. The period of seven minutes begins when the transponder is set to 7600 and this should be done as soon as the pilot has detected communications failure.
If failure occurs when the aircraft is following a notified departure procedure such as a Standard Instrument Departure (SID) and clearance to climb, or re-routing instructions have not been given, the procedure should be flown in accordance with the published lateral track and vertical profile, including any stepped climbs, until the last position, fix, or waypoint, published for the procedure, has been reached. Then, for that part of the period of seven minutes that may remain, maintain the current speed and last assigned level or minimum safe altitude if this is higher.
Following the period of seven minutes, adjust the speed and level in accordance with the current flight plan and continue the flight to the appropriate designated landing aid serving the destination aerodrome. Attempt to transmit position reports and altitude/flight level on the appropriate frequency when over routine reporting points.
If being radar vectored, or proceeding offset according to RNAV, without a specified limit, continue in accordance with ATC instructions last acknowledged for three minutes only and then proceed in the most direct manner possible to rejoin the current flight planned route. Pilots should ensure that they remain at, or above, the minimum safe altitude.
Comply with the loss of communications procedures notified for the destination aerodrome in the AD 2 section of the UK AIP.
Arrange the flight to arrive over the appropriate designated landing aid serving the destination aerodrome as closely as possible to the ETA last acknowledged by ATC. If no such ETA has been acknowledged, the pilot should use an ETA derived from the last acknowledged position report and the flight-planned times for the subsequent sections of the flight.
Arrange the flight to arrive over the appropriate designated landing aid serving the destination aerodrome at the highest notified Minimum Sector Altitude taking account of en-route terrain clearance requirements.
If following a notified Standard Arrival Route (STAR), after the seven minute period detailed in paragraph (b) (i) has been completed, pilots should arrange descent as close as possible to the published descent planning profile. If no descent profile is published, pilots should arrange descent to be at the minimum published level at the appropriate designated Initial Approach fix.
On reaching the appropriate designated landing aid serving the destination aerodrome, begin further descent at the last acknowledged EAT. If no EAT has been acknowledged, the descent should be started at the ETA calculated in (e) (i), above, or as close as possible to this time. If necessary, remain within the holding pattern until the minimum holding level, published for the facility, has been reached. The rate of descent in holding patterns should not be less than 500 FT per minute. If ‘Delay not determined’ has been given, do not attempt to land at the destination aerodrome, divert to the alternate destination specified in the current flight plan or another suitable airfield.
Carry out the notified instrument approach procedure as specified for the designated navigational aid and, if possible, land within 30 minutes of the EAT or the calculated ETA. When practical, pilots should take account of visual landing aids and keep watch for instructions that may be issued by visual signals from the ground.
3.4.3
Actions taken by ATC
-
As far as is practical, ATC shall maintain separation between the aircraft experiencing the communication failure and other aircraft based on the assumption that the aircraft will operate in accordance with published radio communication failure procedures. This includes making allowance for the fact that an aircraft following an approach, whether or not it has received a landing clearance, may either land or may carry out the missed approach procedure.
-
ATC will assume that an aircraft's receiver may be functioning and will transmit instructions for routing and other relevant information such as the EAT, weather information, altimeter settings and runway in use at destination (or alternate) aerodromes.
-
ATC will use all means possible to monitor the flight's progress and inform other flights where necessary.
-
ATC will attempt to re-establish communications with the pilot by monitoring standby frequencies (where available) and by contacting the aircraft operator, or handling agent or by use of ACARS/Data Link when available.
-
ATC will co-ordinate the flight with other ATC agencies as required.
-
If the flight re-establishes communications with an ATC unit during flight, or after the aircraft has landed, the ATC unit will relay the pilot's intentions, or that the aircraft has landed, to the ATC Unit that was providing an ATS when the communications failure occurred.
-
If the aircraft's progress cannot be monitored by radar and there has been no other indication of the aircraft's progress, or landing, normal overdue action will commence 30 minutes after the ETA for the destination airfield.
3.5 Use of Airborne Collision Avoidance Systems (ACAS) in the Scottish FIR/UIR and the London FIR/UIR
3.5.1
General
3.5.1.1 ACAS indications shall be used by pilots in the avoidance of potential collisions, enhancement of situational awareness, and the active search for, and visual acquisition of, conflicting traffic. The ability of ACAS to fulfil its role of assisting pilots in the avoidance of potential collisions is dependent on the correct and timely response by pilots to ACAS indications.
3.5.1.2 The Traffic Alert and Collision Avoidance System (TCAS) II is accepted by the Civil Aviation Authority (CAA) as a suitable ACAS system provided its installation is certificated by the State of Registry, and that its operation by flight crew is in accordance with appropriate operating instructions.
3.5.2
Procedures to be Established
3.5.2.1 An operator shall establish procedures to ensure that:
When ACAS is installed and serviceable, it shall be used in flight in a mode that enables Resolution Advisories (RAs) to be produced unless to do so would not be appropriate for conditions existing at the time, and
When undue proximity to another aircraft is detected by ACAS, the commander or the pilot to whom conduct of the flight has been delegated shall ensure that corrective action is initiated immediately to establish safe separation.
The circumstances when it is appropriate to operate ACAS in the Traffic Advisory (TA)-only mode are specified in the Flight Operations Manual. This should be limited to particular in-flight failures, during take-offs or landings in limiting performance conditions (for example at high altitude airports), and locations where States have approved specific procedures permitting aircraft to operate in close proximity, only.
3.5.3
TCAS II Operating Characteristics
3.5.3.1 TCAS II will issue a TA only when another aircraft with a compatible operating transponder is close in both range and altitude. If the transponder in the potentially conflicting aircraft is providing altitude data, an RA may be issued.
3.5.3.2 TAs and RAs can be issued on the basis of 'time to closest point of approach (CPA)' or 'fixed distance' thresholds being penetrated. On most occasions, TAs and RAs will be issued on the 'time to CPA' basis, but in RVSM penetration of airspace fixed range and altitude thresholds are likely to be a more frequent cause.
Note: In cases where a vertical speed of closure causes RAs to be issued, TCAS II in the climbing/descending aircraft may advise a reduction in the climb or descent rate, whilst TCAS II in the other aircraft may advise a 'Climb' or 'Descend' RA. If the climbing/descending aircraft in this pair is diverging in range at a slow rate, the 'Climb' or 'Descend' RA issued to the Flight Crew in the other aircraft may remain displayed for several minutes, even though the former has levelled off at its cleared flight level. Although this particular circumstance is likely to be rare, even when it does occur, excessive altitude excursions need not result.
3.5.4
Operation of Aircraft When ACAS II is Unserviceable
3.5.4.1 The current TCAS II Minimum Equipment List permits TCAS II equipped aircraft to operate for up to 10 days with the equipment out of service. This position will be kept under review.
3.5.4.2 Due to the safety benefits arising from TCAS operations and the collaborative way in which it arrives at collision avoidance solutions any aeroplane with an unserviceable transponder as well as an unserviceable TCAS will not be permitted in UK airspace for which mandatory carriage of a transponder is required.
3.5.5
Operation of TCAS II in RVSM Airspace
3.5.5.1 Above FL 290, TAs and RAs are most likely to occur in airspace where aircraft change altitude to reduce separation from 2000 FT to 1000 FT: this airspace is described as a 'Transition Area'. Specifically:
TAs can be expected when aircraft vertically separated by 1000 FT pass each other. If the speed at which they pass is low, such as when one is overtaking the other, TAs may be intermittent or they may last for long periods.
RAs can be expected when the vertical speed of closure, which may be the sum of the vertical speeds of both aircraft or the vertical speed of one of the aircraft, exceeds approximately 1500 FT/min. RAs might also be issued when either aircraft experiences turbulence sufficient to cause TCAS to project the vertical separation between both aircraft to be less than 800 FT at CPA, or when a 'soft altitude hold' function in either aircraft achieves the same result.
3.5.6
Guidance for Aircraft Operators and Flight Crews
3.5.6.1 Flight Crews can reduce the likelihood of TAs and RAs occurring above FL 290 where separation is less than 2000 FT vertically and 5 NM horizontally by confining vertical speeds to less than 1500 FT/min. Desirably, the vertical speed should be between 500 and 1000 FT/min.
3.5.6.2 The TCAS II function control selector should not be moved from the 'TA/RA' or 'Normal' position upon entering RVSM Airspace. Although it is implicit that such TAs and RAs as have been described could be termed 'unnecessary', this might not always be the case. For this reason, Flight Crews would be unwise either to disable an effective collision avoidance device without sound reason, or to assume that any TA or RA issued in this airspace is other than genuine.
3.5.6.3 Flight Crews shall not manoeuvre an aircraft solely in response to a TA. TAs are intended to alert the pilot to the possibility of an RA, and to assist in visual acquisition of conflicting traffic. However, visually acquired traffic may not be the same traffic causing a TA, and visual perception of an encounter may be misleading, particularly at night.
3.5.6.4 In the event that an RA is issued, Flight Crews shall:
Respond immediately and manoeuvre as indicated by the ACAS unless doing so would jeopardise the safety of the aircraft;
follow the RA even if there is a conflict between that RA and an air traffic control (ATC) instruction to manoeuvre;
not manoeuvre in the opposite sense or direction to that of the RA;
limit RA manoeuvres to the minimum extent necessary to comply with the RA.
3.5.6.5 Flight Crews should note that:
Other critical warnings such as Stall Warning, Windshear Warning and Ground Proximity Warning Systems have priority over ACAS.
visually acquired traffic may not be that causing an RA, as the visual perception of an encounter may be misleading, particularly at night.
ATC may not know when an ACAS system issues an RA. It is possible for ATC to issue instructions to an aircraft that are unknowingly contrary to RA instructions on that aircraft. Therefore, it is essential that ATC be notified when an ATC instruction is not being followed because it conflicts with an RA.
a manoeuvre opposite to the sense of an RA may result in a reduction in vertical separation with the ‘threat’ aircraft and therefore must be avoided at all times; this is particularly true in the case of an ACAS-ACAS co-ordinated encounter, when the RAs complement each other in order to reduce the potential for collision. Manoeuvres, or lack of manoeuvres, that result in vertical rates opposite to the sense of an RA could result in a collision with the threat aircraft.
3.5.6.6 A pilot who has deviated from an air traffic control instruction or clearance in response to an RA shall:
As soon as possible, as permitted by flight deck workload, notify the appropriate ATC unit of the RA, including the direction of any deviation from the current ATC instruction or clearance.
when they are unable to comply with a clearance or instruction that conflicts with an RA, notify ATC as soon as possible consistent with flying the aircraft.
promptly comply with any modified RAs.
return to the terms of the ATC instruction or clearance when the conflict is resolved.
after initiating a return to, or resuming the current clearance, notify ATC as soon as possible consistent with flying the aircraft.
3.5.6.6.1 Verbal reports should be made to Air Traffic Control at the first practicable moment and written reports submitted to the designated Authority as soon as possible after the flight has ended.
3.5.7
Guidance for Air Traffic Service Providers and for Air Traffic Controllers
3.5.7.1 The operation of TCAS II equipment will affect ATC operations to some extent, irrespective of the type of airspace. ATC will expect Flight Crew to react to RAs and to notify any manoeuvres initiated in response to RAs in accordance with standard practice. The Manual of Air Traffic Services Part 1, Section 1, Chapter 9 provides information on TCAS II to Air Traffic Controllers: it reiterates the phraseology that Flight Crews will use and the replies that Air Traffic Controllers should make.
3.5.7.2 It will be apparent from paragraph 3.5.5.1 that TAs will be more frequent in North Atlantic RVSM Airspace than elsewhere. Air Traffic Controllers should be aware of this and, where possible, be prepared to provide requested traffic information to Flight Crews.
3.5.7.3 As pilots are not required to take avoiding action on the basis of TA information alone, ATC does not expect requests for traffic information to be made unless the other aircraft cannot be seen and the pilots believe their aircraft is about to be endangered.
3.5.7.4 ATC expects pilots to respond immediately to an RA. Pilots are expected to restrict their RA manoeuvres to the minimum required to resolve the confliction, advise the Air Traffic Control Unit as soon as is practical thereafter and return to their original flight path as soon as it is safe to do so.
3.5.7.5 Pilots should be aware that any deviation from an ATC clearance has the potential to disrupt the controller's tactical plan and may result in a reduction of standard separation between aircraft other than those originally involved. It is vital that Flight Crew maintain a good look out and return to their original flight path as soon as it is safe and practical to do so.
3.6 Emergency Descents
3.6.1
General
3.6.1.1 The requirement to carry out an emergency descent may be necessary to ensure the safety of an aircraft and its occupants, and can sometimes be required with little or no notice. In busy and congested airspace, sudden changes of level can lead to unexpected interactions with other aircraft in the vicinity.
3.6.2
Turning-off or Remaining on Track in UK Controlled Airspace
3.6.2.1 UK Controlled Airspace is complex and congested, and traffic is often oriented on ATS routes in certain directions or flows. Therefore, if able, pilots should remain on the assigned route or track whilst carrying out the emergency descent, unless to do so would endanger the aircraft.
3.6.2.2 If a turn away from an assigned route or track is initiated, pilots should note that they may not be aware of traffic in their proximity (especially if flying on an assigned heading); nor of aircraft below them, not on the selected frequency, or in adjacent airspace sectors. However, it is ultimately the pilot’s responsibility to take the action most appropriate in the circumstances.
3.7 Diversion
3.7.1 Diversion is the act of flying to an aerodrome other than the planned destination with the intention of landing there.
3.7.2 Normally diversion is made when one of the following circumstances occurs at the planned destination:
The weather is reported to be below the operating company's minima;
there are obstacles on the manoeuvring area constituting a hazard to landing aircraft which cannot be cleared within a reasonable time;
there is a failure of an essential ground aid which is required for the landing;
there is likely to be an unacceptable delay to landing.
3.7.3 Diversion may be originated by either the pilot or his operating company, or exceptionally by ATC.
3.7.3.1 When a pilot decides to divert he should inform ATC. ATC will, if possible, advise his operating company or a nominated addressee of his diversion when this is specifically requested by the pilot.
3.7.3.2 An operating company proposing to divert one of its aircraft should consult ATC before any decision on diversion is passed to the pilot. The message to the pilot will be in this form:
'Company advise divert to . . . . . (aerodrome). Weather at . . . . . (diversion aerodrome) . . . . . Reason for diversion . . . . . (clearance instructions). Acknowledge'.
The pilot should either follow this advice or if he is unable to do so, give his reasons and state what he intends to do.
3.7.3.3 In exceptional circumstances, it may be necessary for ATC to advise a pilot to divert before being able to consult his operating company. In such a case, the company will be told as soon as possible and the message to the pilot will be in the form:
'Request divert to . . . . . (aerodrome). Weather at . . . . . (diversion aerodrome) . . . . . Reason for diversion . . . . . (clearance instructions). Acknowledge'.
If the pilot is unable to comply with this request, he should give his reasons and state his intention.
3.8 Low Level Cross-Channel Operations - UK/France
3.8.1 Pilots undertaking Cross-Channel flights are reminded that a flight plan MUST be filed for all flights crossing FIR boundaries between the UK and France.
3.8.2 When filing the flight plan with the UK and French Authorities, pilots are to ensure that well defined significant points/features, at which the aircraft will cross the UK and French coast-lines, are included in Item 18 (Other Information) of the flight plan form (eg Beachy Head, Berck-sur-Mer, Lydd, Boulogne, Dover, Cap Gris Nez, etc). This is for Search and Rescue purposes but will also assist ATC.
3.8.3 Pilots should plan their flights, where possible, at such altitudes which would enable radio contact to be maintained with the appropriate ATC Unit whilst the aircraft is transitting the Channel. In addition, the French Authorities have requested that aircraft fly at altitudes which will keep them within Radar cover. The carriage of Secondary Surveillance Radar (SSR) equipment is recommended.
3.8.4 Position reports are required when crossing the coast outbound, inbound and when crossing the FIR Boundary.
3.8.5 Pilots undertaking Cross-Channel flights under IFR, are reminded that the normal IFR Rules will apply particularly regarding altitudes and flight levels. Pilots are also reminded that the IMC rating is not recognized by the French Authorities.
4 Arrangements for Particular Types of Flight (Non-Standard, Non-Deviating, Unusual, Royal, Observation, Special, VFR Access to Class C Airspace Above FL 195, and Civilian Formation Flights)
4.1 Non-Standard Flights (NSFs) in Controlled Airspace
4.1.1 A Non-Standard Flight (NSF) in Controlled Airspace is an aerial task that may not necessarily follow published routes or notified procedures; a formation flight of civil aircraft other than for VFR transit of CTA/CTR/TMA; or flights to and from a temporary landing site for multiple short term operations. For test flights which take place within CAS and use the ATS route network, please see section 4.9.
4.1.1.1 Applications for NSFs within Controlled Airspace should primarily be made via the NATS Non-Standard Flight Application website (www.nats.co.uk/nsf) with the minimum 21 or 28 days notice (see paragraphs 4.1.2 and 4.1.6).
See Swanwick (Mil) Sector Dimensions chart at ENR 6-12.
4.1.1.2 Applicants using the website based application should ensure that the file sizes do not exceed 5MB. Zipped files are acceptable.
4.1.2 New applications or a renewal of a previously approved application shall give a minimum of
21 days notice and include the information listed below (Any modification to a previously approved NSF application, without a change to the validity date, shall give a minimum of 10 days notice from the date of modification):
Purpose of flight;
the area of operation and proposed tracks to be flown, to include graphical depiction on a suitable aeronautical chart plus a list of National Ordnance Survey Grid and/or WGS84 co-ordinates detailing the requested areas of operation in relation to Controlled Airspace;
estimated duration of aerial task;
operating levels;
aircraft type, callsign and registration letters on any aircraft likely to be used;
aerodrome of departure;
planned date of operation and requested validity period;
communications equipment (including transponder fit).
4.1.2.1 Those applications which are agreed will be allocated a non-standard flight reference number. This is only an approval in principle and prior clearance must be obtained from the appropriate ATC Watch Supervisor on the day. This is normally obtained by telephone 1 hour prior to departure. However, since many tasks are weather-dependent, some have to be abandoned after the aircraft is airborne. To overcome the particular difficulty of having to land and co-ordinate another detail by telephone, the following procedures may be adopted by pilots of those NSFs which have been previously allocated a NSF number by London Area Control (Swanwick) or London Terminal Control (Swanwick), and who wish to abandon the original task co-ordinated prior to take-off and proceed to another location.
4.1.2.1.1 The aircraft commander will establish RTF contact on the London FIS frequency (callsign 'London Information') appropriate to the area of the country over which the new task is required to be flown, prefixing the message with the phrase 'Non-Standard Flight Request'. The following information will then be passed to the Flight Information Service Officer (FISO):
The Non-Standard Flight number;
the requested area of activity (this is essential as many NSF numbers refer to several sites);
ETA at site;
the requested Flight Level or Altitude for the task;
the duration of the task;
the aircraft callsign.
4.1.2.1.2 The FISO will relay these details to the appropriate ATC Unit and, in due course, will advise the pilot whether or not the NSF is approved, together with any special conditions and a contact frequency for the ATC Unit concerned. Pilots should not call for an approval directly on an operational ATC frequency. This is particularly important in the case of frequencies in use by London Terminal Control (Swanwick) or London Area Control (Swanwick).
4.1.2.1.3 In the case of NSFs affecting Airspace for which London Terminal Control (Swanwick) is responsible, it may sometimes be necessary for the pilot to land at a convenient aerodrome and telephone Terminal Control Senior Watch Assistant to discuss the requirements of the task in detail.
4.1.2.1.4 Operators are to note that in no circumstances can any discussion be entered into on any frequency in the event that permission is refused or withdrawn.
4.1.3 ATC clearance does not imply exemption from the requirements of the Air Navigation Order (ANO) or the Rules of the Air Regulations. Applications for flights which require exemption or written permission under the ANO are to be forwarded to:
Post: The Civil Aviation Authority, Flight Operations Division, Aviation House, Gatwick Airport South, West Sussex, RH6 0YR
4.1.4 Because of the nature of ATC operations (and notwithstanding the requirements of GEN 1.5, paragraph 5.3 concerning the carriage of SSR transponders), the approval of an application for a Non-Standard Flight will depend on the carriage of SSR transponder equipment normally with Mode C.
4.1.5 Due to the inherent difficulties of handling a formation flight in a busy traffic situation, pilots should be aware that it may not always be possible to issue an ATC clearance at the time requested.
4.1.6
Enhanced Non-Standard Flights (ENSFs) - Entry into EGR156 (Windsor Castle)/EGR157 (Hyde Park)/EGR158 (City of London)/EGR159 (Isle of Dogs) Restricted Areas
4.1.6.1 For those aircraft not already exempted (see individual entry for Restricted Area at ENR 5.1), ENSFs are required for flights within EGR156, EGR157, EGR158 and EGR159. Requests should be made using the NSF website (www.nats.co.uk/nsf) as detailed at paragraph 4.1.1.1 giving a minimum of 28 days notice. Any modification to a previously approved ENSF application shall give a minimum of 28 days notice from the date of modification.
4.1.6.2 ENSFs are subject to security considerations by the Metropolitan Police and may be refused on public interest grounds.
4.1.6.3 Once the security process is complete and London Terminal Control (Swanwick) provisional ATC approval in principle is granted, an 'ENSF Notification - Approval' form will be returned to the operator. Details of how to obtain a Metropolitan Police authorisation number for an ENSF and the ATC tactical approval on the day of flight are detailed on the 'ENSF Notification - Approval' form.
4.1.7
Single-Engine Fixed Wing Aircraft Over Central London
4.1.7.1 With the exception of the Northolt RMA and the Local Flying Areas at Denham and Brooklands (see AD 2.EGLL AD 2.22), NSF or ENSF permissions will not be granted to single-engine fixed wing aircraft requesting to operate within those parts of the London and London City Control Zones between a North-South line extending through the LON DME and a North-South line extending through the LCY NDB. In accordance with a directive from the CAA Safety and Airspace Regulation Group (SARG), applications which fall within the above criteria will be refused upon application to the NSF Coordinator due to the inability of such aircraft, in the view of the CAA, to be able to comply with SERA.3105 Minimum Heights.
4.1.8
Unmanned Aircraft Systems (UAS)
4.1.8.1 Any unmanned aircraft flight within a Flight Restriction Zone (FRZ) requires permission from the relevant ATSU or aerodrome operator using the appropriate process. Permission to operate within an FRZ should be obtained from the aerodrome directly, or through a suitable electronic service.
4.1.8.2 Permission to operate within the FRZ must be issued by either:
The ATC Unit; or
The Aerodrome Flight Information Service (AFIS), if no ATC or outside the operating hours of ATC; or
The Aerodrome Operator, if there is no ATC or AFIS, or outside the operating hours of ATC or AFIS.
4.1.8.3 The FRZ consists of:
A zone with the same dimensions as the notified Aerodrome Traffic Zone (ATZ); and
The Runway Protection Zones (RPZ); and
Any Additional zones, defined in the AIP .
All elements of the FRZ are active H24, regardless of the hours of operation of the aerodrome, or the ATZ activation.
4.1.8.4 Protected Aerodromes are those which are certified, Government, national licensed or otherwise as specifically prescribed. A list of aerodromes which are certified aerodromes and national licensed can be found within the AIP Aerodrome section (Part 3 AD 2).
A list of Government aerodromes can be found in the Military AIP.
4.1.8.5 A permission to operate within an FRZ is given conditionally upon the unmanned aircraft operation remaining entirely within the limits of the stated lateral and vertical operating area and that no safety assurance against other UAA taking place in the same area is given or implied. Compliance with the UK Air Navigation Order is required at all times.
4.1.8.6 Unmanned aircraft flights above 400 FT require a CAA authorisation, including those within an FRZ, which will also require permission from the aerodrome. A CAA authorisation to operate above 400 FT does not guarantee permission will be given by an aerodrome for the operation.
An A/G Radio service operator may not grant permission for an unmanned aircraft to operate within the FRZ.
Government aerodromes retain the right to refuse unmanned aircraft flight above 400 FT. To seek approval for any activity above 400 FT, early liaison with Government aerodromes is advised.
4.1.8.7 Operators are reminded of the applicability of the new UAS regulations, which are applicable from 31 December 2020. Further details can be found in CAP 722.
4.1.8.8 FRZ Permission Requirement Summary .
This table summarises when a permission is required from an aerodrome to operate within an FRZ. Other authorisations from the CAA may also be required.
| Within the FRZ | Within Operating Hours of Air Traffic Control Unit (ATC) or Aerodrome Flight Information Service (AFIS) | Outside Operating Hours of ATC/AFIS (or no ATC/AFIS present) |
|---|
| 400 FT or Below | Permission required from ATC/AFIS unit | Permission required from aerodrome operator |
| Above 400 FT | Authorisation required from CAA UAS Unit AND Permission required from ATC/AFIS Unit | Authorisation required from CAA UAS Unit AND Permission required from aerodrome operator |
4.1.8.9 It is highly recommended that, when an unmanned aircraft flight takes place at 400 FT or more above aerodrome level, within an FRZ, outside the ATZ, this shall be notified by NOTAM or other appropriate means, which can be requested via AROps@caa.co.uk. This will normally be stated as a condition within the CAA authorisation to operate above 400 FT. Upon application for an unmanned aircraft flight within such an area, the aerodrome operator or ATSU should direct the applicant to the CAA to request a NOTAM, in addition to their own permission. A NOTAM issued for such a flight does not constitute permission to operate within an FRZ, this must still be obtained from the aerodrome operator or ATSU as appropriate. Any NOTAM request for such an operation, submitted to the CAA should include either documentation of the permission to operate within the FRZ, or an agreement in principle, to operate within the FRZ.
4.1.8.10 It is highly recommended that, when any unmanned aircraft flight is permitted anywhere within an FRZ outside the hours of operation of any ATSU at the aerodrome, this shall be notified by NOTAM or other appropriate means which, for the portion of the RPZ outside the ATZ, can be requested via AROps@caa.co.uk.
4.1.8.11 UAS Operators should note that the AROps@caa.co.uk email address is not an H24 service and operates within normal office hours. NOTAMs may be requested by aerodromes for UAS operations within the ATZ portion of the FRZ directly to the NOF. NOTAMs for flights outside the ATZ portion of the FRZ must be obtained by the AROPS@caa.co.uk email address. Aerodromes which are not licensed may request NOTAMs from the NOF. All operations should be planned with sufficient notice to achieve a NOTAM where necessary.
4.1.8.12 There may be occasions where, for urgent operational reasons, UAS operations need to occur within an FRZ at short notice, for example, an emergency police response. The requirements outlined in paragraphs 4.1.8.1 to 4.1.8.8 still apply, and permission must be sought. Paragraphs 4.1.8.9 to 4.1.8.11 are advisory, and must be followed where possible. Emergency service operations responding to an incident with little notice, may elect not to issue a NOTAM if it is not possible.
4.1.8.13 FRZ NOTAM Requirement Summary.
| Within Operating Hours of Air Traffic Service Unit (Air Traffic Control, Aerodrome Flight Information Service or Air Ground Radio service) | Outside Operating Hours of Air Traffic Service Unit (Air Traffic Control, Aerodrome Flight Information Service or Air Ground Radio service) |
|---|
| Below 400 FT | Above 400 FT | Below 400 FT | Above 400 FT |
|---|
| ATZ Portion of FRZ | | | NOTAM (Requested by aerodrome via NOF) | NOTAM (Requested by aerodrome via NOF) |
| Portion of FRZ outside the ATZ | | NOTAM (requested in advance via AROps@caa.co.uk) | | NOTAM (requested in advance via AROps@caa.co.uk) |
Note: There may be occasions other than the circumstances described above, when a NOTAM is required. These should be determined by the UAS operator, the CAA and the aerodrome where appropriate. Such circumstances include the flight of larger unmanned aircraft, or BVLOS operations.
4.1.8.14 In the event that a UAS operator requests permission to operate within two or more FRZs simultaneously, where they overlap, permission must be requested from all aerodromes concerned. Any one aerodrome may not give unilateral permission for the flight to occur, unless such an agreement is in place between the aerodromes.
4.1.8.15 An aerodrome may only issue a permission to a UAS operator to access their FRZ, and may not issue a permission for an entire UAS operation, which may require additional authorisations from the CAA and other agencies.
4.1.8.16 Flights by unmanned aircraft into Restricted Areas EGR156, EGR157, EGR158 and EGR159 within the London and London City Control Zones require specific approval via the ENSF process (see paragraph 4.1.6).
4.1.9
Unusual Aerial Activities Both Within and Outside Controlled Airspace
4.1.9.1 Normally, requests for the approval of Unusual Aerial Activities remaining within Controlled Airspace at all times are treated by the controlling authority as Non-Standard Flights.
4.1.9.2 Requests for the approval of Unusual Aerial Activities (UAA) operating within Controlled Airspace (Class A-E) and Class G airspace are treated differently from the Non-Standard Flight (NSF) type. Such UAAs are more complex and time-consuming to resolve because of the need for additional negotiation needed between ATC and airspace users, and should be notified to ATC at the earliest opportunity. A UAA of this nature is processed by the CAA Airspace Regulation section, which consults all agencies affected, arranges NOTAM action, and publishes an Airspace Coordination Notice (ACN). The ACN details the agreements reached about the activity inside and outside Controlled Airspace and reflects the NSF approval issued by the relevant controlling authority.
4.1.9.3 Details of UAAs/NSFs operating within Controlled Airspace (Class A-E) and Class G airspace are to be submitted as per paragraph 4.1.2 with a copy to:
Post: Airspace Regulation (Utilisation), Aviation House, Gatwick, RH6 0YR
Phone: 01293-983880
Email: arops@caa.co.uk
4.1.10
VFR Flight in Class C Airspace Above FL 195
4.1.10.1 VFR flight by civil aircraft above FL 195 shall not be permitted unless it has been accorded specific arrangements by the appropriate ATS authority. VFR flight shall only be authorised:
In reserved airspace;
Outside reserved airspace up to FL 285, and then only when authorised in accordance with the procedures detailed for Non-Standard Flights in Controlled Airspace.
4.1.10.2 If utilising permanently established reserved airspace, the established booking procedures for that airspace should be followed. If there is a need for the establishment of temporary reserved areas then procedures for conducting Unusual Aerial Activities in Controlled Airspace shall be followed as detailed in paragraph 4.1.9. Standing arrangements for temporary reserved areas for gliding in Class C airspace are shown at ENR 1.1, paragraph 1.11.
4.1.10.3 It is anticipated the demand for VFR access outside of an airspace reservation will be minimal. Such access will be accommodated within the context of safety, capacity and effect on the ATS network as a whole; consequently VFR access to the ATS route structure is only likely to be permitted in exceptional circumstances. In this case the appropriate civil ATC Unit will coordinate provision of ATS. Operators seeking to operate in such areas should contact the appropriate ACC Operations Department as detailed at paragraphs 4.1.1 to 4.1.5. Applications for VFR flight to avoid IFR ATS route flow restrictions will not be granted.
4.1.10.4 Operators seeking localised VFR flight above FL 195 not requiring reserved airspace and clear of the ATS route structure should contact the relevant Military Supervisor located at London Area Control (Swanwick) who will co-ordinate access arrangements and military ATC provision within unit capacity. Contact details are shown at paragraph 4.1.1.1 (d) and (e). Such flights shall only be permitted where procedures are established with the controlling authority.
Note: Specific arrangements for gliding operations above FL 245 are shown at ENR 1.1, paragraph 1.11.
4.1.11
VFR Flight in Class C Areas of Delegated ATS
4.1.11.1 Charts depicting these areas are detailed at ENR 6-2 pages. These delegated areas of ATS are busy international interfaces. Consequently, approval for VFR flight will only be granted in exceptional circumstances and after co-ordination with and agreement of the respective ATS provider. Applications for VFR access to these areas should in the first instance be made to AUS as detailed in paragraph 4.1.9.
4.2 Non Deviating Status (NDS)
4.2.1 NDS may be agreed by prior arrangement with the appropriate controlling authorities for certain flights within Controlled Airspace excluding in the UIR active Danger and Military Training Areas.
4.2.2 The requirement for NDS may be expressed as all, or part, of a notified flight profile and not merely for a constant heading and, or, flight level. Application for NDS should only be made where an inability to maintain specific track(s) and or flight level(s) could render a task operationally ineffective. NDS would not be appropriate for, nor would it be granted to, GAT aircraft carrying freight or passengers between destinations or GA aircraft general handling etc or in transit.
4.2.3 NDS affords priority of passage over all other OAT and GAT except for: aircraft in emergency; Royal Flights; Air Defence Priority Flights; GAT with higher civil priority category or other higher priority Special flights.
4.2.4 The Airspace Regulation (Utilisation) (AR(U), is the central authority for authorising NDS and is the focal point for NDS applications, inter unit negotiations and approvals.
4.2.5 AR(U) normally requires a minimum of 21 days notice of pre-flight requests for NDS in order to obtain agreement from the affected Air Traffic Service Units (ATSUs) and, or, Airborne Surveillance and Control (ASAC) Units. A request for NDS should include:
Operating authority, including a point of contact;
type of aircraft operation (e.g. flight trial, calibration etc);
reference number or other discrete nomenclature;
aircraft registration(s) and/or callsign(s);
details of flight(s);
departure aerodrome and destination;
route or area;
profiles (if appropriate);
times;
altitudes or Flight Levels;
facilities to be used (if appropriate);
any non-ATC agencies involved;
any specific requirements eg frequencies to be used etc.
details of any specific flexibility, limitation or critical aspect.
Shorter notice applications may be considered on merit, but AR(U) may direct aircraft operating authorities to refer their requests for NDS direct to the appropriate ATSU(s) or ASAC unit(s) involved if the application cannot be processed in time by AR(U).
4.2.6 Units will attempt to agree to short notice requests for NDS but, if given insufficient time, may decline or modify the request. Profile adjustments may, in any event, need to be negotiated if such changes would result in less disruption to other traffic.
4.2.7 Flights granted NDS will remain under radar control or procedural service. If in the interest of flight safety it should become necessary to give NDS flights avoiding action, such instructions from a controller are Mandatory.
4.3 Unusual Aerial Activities (UAA) Outside Controlled Airspace
4.3.1 A UAA may constitute a hazard if pilots of non-participating aircraft are not aware that it is taking place. The Civil Aviation Authority and in particular Airspace Regulation (Utilisation) (AR(U)) require appropriate prior notification of a UAA to enable either AR(U) to co-ordinate and notify the event, or for the Authority to issue a Permission or Exemption under the Air Navigation Order (ANO) and the Regulations. Event or display organisers are advised to utilise the CAA Publication CAP 403 'Flying Displays and Special Events: A Guide to Safety and Administrative Arrangements'. The document is available from The Stationery Office (Tel: 0870-6005522) and on the CAA web site: http//www.caa.co.uk/publications
4.3.2 Individual participating pilots are advised to check that the event or display organiser has made proper application for any required Permission or Exemption.
4.3.3 While there are many types of UAA, most fall within one of the following categories:
A concentration of aircraft significantly greater than normal, e.g. a Rally or Fly-in;
Activities requiring the issue of a Permission or an Exemption from the ANO and the Regulations, e.g. low flying near assemblies of people, the dropping of articles or parachutists, or balloon or kite flying;
Air Shows, Displays, Air Races and other aeronautical competitions, aerial surveys and avoidance of ground events and hazards;
Activities requiring the establishment and approval of a temporary ATC Unit. (See CAP 670 'ATS Safety Requirements' and CAP 403 for requirements and recommendations). In the case of the provision of a Flight Information Service (FIS) at a temporary FIS Unit refer to CAP 797 'Flight Information Service Officer Manual' and CAP 1032 'Aerodrome Flight Information Service Officer Licensing'. All are available on the CAA web site, as above.
4.3.4 All event or display organisers wishing to arrange a UAA are to use the standard notification forms SRG 1303 (Flying Display Notification Form) or SRG 1304 (Special Events and Unusual Aerial Activity Application Form) as appropriate.
4.3.5 The length of notice required by the Authority and AR(U) is as follows:
UAA at a licensed aerodrome or site where a temporary aerodrome licence is required - 60 days;
UAA at an aerodrome or a site where an aerodrome licence is not necessary - 42 days;
If an activity is intended to attract more than 100 aircraft it is essential that proposals are discussed with both the Aerodrome Standards Department (ASD) and the appropriate Regional Manager - Air Traffic Services (ATS) prior to any firm arrangements being made. These discussions should be initiated at least 90 days prior to the date of the Activity. If the organiser has any doubt on the level or type of Air Traffic Service that should be provided, he/she is strongly recommended to contact the relevant Regional Manager (ATS) for guidance;
If it is intended to establish a Temporary Air Traffic Control Unit (ATCU) at an event, it is essential that organisers refer to the document CAP 670 'ATS Safety Requirements' which contains comprehensive information and requirements for the establishment of such a unit. This document is available on the CAA web site: http//www.caa.co.uk/publications
A provider of Air Traffic Control must be nominated and he/she is required to apply to the appropriate CAA ATSSD Regional Office in advance of the event for unit approval. A copy of the proposed Manual of Air Traffic Services Part 2 (MATS Part 2) should be submitted as soon as possible but no later than 60 days before the event. The format of the MATS Part 2 is laid out in CAP 670 - Part B, Section 2, Annex A to ATC 02 with further information in Part B, Section 1, APP04, Page 3.
Established ATS Units intending to hold a Flying Display or Special Event are required to notify their ATSSD Regional office if the event requires changes to safety related procedures at that unit.
Copies of Form SRG 1417, which also may be used for the application for a temporary VHF frequency, are available from CAA ATSSD Regional Offices or on the CAA web site. A minimum of 90 days notice is required for a temporary assignment of VHF aeronautical channels.
Note: Air Traffic Services Standards Department (ATSSD) - Regional Offices
Post:
Regional Manager ATS
Southern Regional Office, Floor 2W, Aviation House, Gatwick Airport South, West Sussex RH6 0YR.
Tel: 01293-573426.
Fax: 01293-573974.
Post:
Regional Manager ATS
Central Regional Office, Manchester International Office Centre, Suite 5, Styal Road, Wythenshawe, Manchester M22 5WB.
Tel: 0161-499 3055 x242.
Fax: 0161-499 3048.
Post:
Regional Manager ATS
Northern Regional Office, 7 Melville Terrace, Stirling, FK8 2ND.
Tel: 01786-431400.
Fax: 01786-448030.
Post:
ATS Standards Department, Aviation House, Gatwick Airport South, West Sussex RH6 0YR.
Tel: 01293-573329.
Fax: 01293-573974.
See chart at ENR 6-6 for Area of Responsibility of the ATSD Regional Offices.
4.3.6 Display organisers and pilots are advised that, although every effort will be made to deal with late notification forms, no guarantee can be given that they will be processed in time for the event.
4.3.7 Forms SRG 1303 and SRG 1304 can be obtained from the CAA website, and when completed should be returned to:
Post:
Civil Aviation Authority, General Aviation Department, 1W, Aviation House, Gatwick Airport South, West Sussex RH6 0YR
Tel: 01293-573227 / 573517 / 573525
Fax: 01293-573973
To arrive at least 28 days before the event, a copy of the form should be sent to:
Post:
Airspace Regulation, Aviation House, Gatwick, RH6 0YR
Tel: 01293-983880
Email: arops@caa.co.uk
4.3.8 Event or display organisers should note that whenever military aircraft participate in a civil aviation event, the Ministry of Defence (MoD) requires the organiser to complete a special questionnaire which is separate from, and additional to, the notification required by the Authority. Event organisers will receive copies of the military questionnaire from the MoD when the military participation is confirmed. The completed questionnaires are to be sent to AR(U).
4.4 Royal Flights
4.4.1
Introduction
4.4.1.1 A Royal Flight within UK airspace is defined as the movement of an aircraft specifically tasked to carry one or more members of The Royal Family afforded such status by the Director of Royal Travel, The Royal Household.
4.4.1.2 When so directed by the Civil Aviation Authority (CAA) Group Director, Safety & Airspace Regulation Group (GD SARG) or Head of Airspace, Aerodromes and Air Traffic Management (Hd AAA) certain flights within UK airspace by reigning Sovereigns and Heads of State of foreign countries and, where appropriate, Prime Ministers of Commonwealth countries may also be afforded Royal Flight status.
4.4.2
Special ATC Arrangements for Royal Flights in Fixed-Wing Aircraft
4.4.2.1
Establishment of Temporary (Class D) Controlled Airspace (CAS-T)
4.4.2.1.1 Royal Flights in fixed-wing aircraft will, whenever possible, take place within the national ATS route structure. Standard ATC procedures shall be applied to Royal Flights when operating in permanent Class A, C and D Airspace. In all other instances, the airspace around the route will be designated CAS-T.
4.4.2.1.2 CAS-T of appropriate height/width bands, and levels, will be established to encompass any portion of the track and flight level of the Royal aircraft that lies outside of permanent Class A, C and D Airspace or transits through an active Military TRA. Temporary Control Zones and Control Areas will be established, where not permanent/extant, around airfields, with an appropriate level of service provision, used for the departure or arrival of a Royal Flight.
4.4.2.1.3 Regardless of the prevailing meteorological conditions, aircraft shall only fly within CAS-T when ATC clearance has been obtained from the controlling authorities specified in the following sub-paras:
Temporary Control Zones. Temporary Control Zones, Class D, will be established, where appropriate, around airfields of departure and destination where no permanent control zones exist. Control Zones for Royal Flights will extend between 5 and 10 NM radius from the centre of the aerodrome from ground level to an upper level designated for each Royal Flight depend ent upon the Royal aircraft type and the aerodromes surrounding airspace. The Control Zone will be established for a period (for outbound flights) of 15 minutes before, until 30 minutes after, the ETD of the Royal aircraft or, for inbound flights, a period of 15 minutes before, until 30 minutes after, the ETA of the Royal aircraft at the airfield concerned. Overall control of these Control Zones is to be exercised, as appropriate, by the Commanding Officer of a military airfield or the appropriate ATS authority of a civil airfield.
Temporary Control Areas. Temporary Control Areas, dimensions and duration thereof, will be established to meet the specific requirements of a Royal Flight. The controlling authority will be the appropriate civil or military ATCC.
Permanent Control Zones and Areas. The controlling authority will be the designated controlling authority for the Permanent Control Zone or Area and the duration will be as laid down in sub-paras 4.4.2.1.3 (a) and (b). Where an airfield has its own Control Zone, then the requirement to establish a Temporary Control Zone of the dimensions specified in para 4.4.2.1.3 (a) may be waived. The ATC Supervisor is to ensure that, when a Royal Flight is active or expected in the same airspace, Special VFR clearances stipulate conditions that provide separation standards against the Royal Flight mirroring IFR separation standards (para 4.4.2.2.2 refers).
Temporary Controlled Airways. Class D airways will be established to join temporary or permanent Control Zones or Control Areas, as appropriate. Class C airways will be established for transit through an active TRA. Such airspace will be established for 15 minutes before ETA at the start point of the temporary airway until 30 minutes after ETD from the end/departure point of the temporary airway. The lateral dimensions of such airways will be 5 NM each side of the intended track of the Royal Flight and vertical limits will be designated as required. The controlling authority will be the appropriate civil or military ATCC.
4.4.2.1.4 A Temporary Control Zone, Area or airway may be cancelled at the discretion of the Military Commander or Civil ATC Supervisor, as appropriate, when the Royal aircraft has left the temporary zone, area or airway and is established en-route in permanent Class A, C or D Airspace, or has landed.
4.4.2.1.5 Training Flights, including parachute-training flights, by any member of The Royal Family planned and carried out under VFR or IFR, and under the control of an ATCRU or aerodrome radar, will normally be classified as Royal Flights. CAS-T, where required, will be established as agreed by the aircraft operating organisation and CAA Airspace Regulation (Utilisation).
4.4.2.2
Procedures Applicable to Royal Flight CAS-T
4.4.2.2.1 CAS-T will be notified as Class C or Class D Airspace; applicable access criteria and separation standards apply.
4.4.2.2.2 Flights may operate in accordance with SVFR as described in ENR 1.2 para 2 of the UK AIP and CAP 493 (Manual of Air Traffic Services) Part 1, Section 1, Chapter 2, Para 8, within CAS-T CTRs.
4.4.2.2.3 CAS-T established outside of existing Class A/C Airspace is hereby notified respectively as either Control Zones or Control Areas (as appropriate) as defined in the UK Air Navigation Order.
4.4.2.3
Promulgation of Royal Flight Information
4.4.2.3.1 Dissemination of information concerning a Royal Flight is made via a Notification Message on a Royal Flight Collective, giving full flight details. Information on the establishment of CAS-T, including vertical limits, is promulgated by NOTAM.
4.4.3
Royal Flights in Helicopters
4.4.3.1 CAS-T is not normally established for Royal Flights in helicopters, but a degree of protection is provided by the establishment of a Royal Low-Level Corridor (RLLC).
4.4.3.2 A RLLC is marked by a series of waypoints and will be promulgated by Notification Message and are applicable to military aircraft only.
Waypoints, approximately 20 minutes flying time apart, will coincide with turning points. The Notification Message will indicate the ETDs/ETAs for given check-points.
Within the RLLC, protected sectors, applying to military aircraft only, are established extending 5 NM either side of the helicopter’s intended track and from ground level up to 1000 FT above the maximum cruise altitude.
In accordance with Military Regulations (RA 3237), prior to entering and when operating inside RLLCs, controllers and pilots of military aircraft should ensure that the military aircraft is in receipt of an ATS (either under Visual Flight Rules (VFR) or Instrument Flight Rules (IFR)) from:
The same Air Traffic Control (ATC) unit that is controlling the Royal Helicopter; or
Another ATC unit that has established radar contract with the Royal Helicopter.
In addition to the requirements at 4.4.3.2(c), standard separation should be applied between military aircraft and the Royal Helicopter in accordance with Military Regulation RA 3228, with the following exceptions:
Light aeroplanes and helicopters operating under VFR with an Indicated Air Speed of 140 KT or less should be provided with sufficient traffic information to assist the military pilots to keep well clear of the Royal Helicopter; or
Military aircraft operating VFR above 140 KT with the approval of the Royal Helicopter Commander.
4.4.3.3 The Notification Message will include a list of nominated aerodromes from which pilots may obtain information on the progress of the Royal Helicopter.
4.4.4
Royal Flight Callsigns
4.4.4.1 The flight plan aircraft identification and the radiotelephony designators for flights flown in aircraft of No. 32 (The Royal) Squadron, the King’s Helicopter Flight (TKHF) or in civilian chartered aircraft are as follows:
Royal Flights. Royal flight callsigns are as follows:
No. 32 (The Royal) Squadron (See note). The 3-letter operator designator KRF followed by an identification number and the letter R, eg KRF 1R, and the radiotelephony callsign ‘KITTYHAWK’ followed by an identification number and the letter R.
TKHF. The 3-letter designator TKF followed by an identification number and the letter R, eg TKF 1R, and the radiotelephony callsign ‘RAINBOW’ followed by an identification number and the letter R.
Civilian Chartered Aircraft. The 3-letter designator KRH followed by an identification number and the letter R, eg KRH 1R, and the radiotelephony callsign ‘SPARROWHAWK’ followed by an identification number and the letter R.
Flights by Passengers entitled to CAA Priority. Callsigns for flights by aircraft carrying passengers entitled to CAA priority are as follows:
No. 32 (The Royal) Squadron (See note). The 3-letter operator designator KRF and the radiotelephony callsign ‘KITTYHAWK’ followed by an identification number.
TKHF. The 3-letter operator designator TKF and the radiotelephony callsign ‘RAINBOW’ followed by an identification number and the letter S.
Civilian Chartered Fixed-wing Aircraft. The 3-letter operator designator KRH and the radiotelephony callsign ‘SPARROWHAWK’ followed by an identification number.
Civilian Chartered Rotary-wing Aircraft. The 3-letter operator designator KRH and the radiotelephony callsign ‘SPARROWHAWK’ followed by an identification number and the letter S.
Positioning Flights. Callsigns for positioning flights are as follows:
No. 32 (The Royal) Squadron (See note). The 3-letter operator designator RRF and the radiotelephony callsign ‘KITTY’ followed by an identification number.
TKHF. The 3-letter operator designator will be TKF and the radiotelephony callsign ‘RAINBOW’ followed by an identification number.
Civilian Chartered Fixed-wing Aircraft. The normal aircraft callsign will be used.
Civilian Chartered Rotary-wing Aircraft. The 3-letter operator designator KRH and the radiotelephony callsign ‘SPARROWHAWK’ followed by an identification number.
Other Flights by Aircraft of No. 32 (The Royal) Squadron (See note). All other flights carried out by No. 32 (The Royal) Squadron will use the 3-letter designator RRR and the radiotelephony callsign ‘ASCOT’ followed by the required identification number.
Helicopters flown by HRH The Duke of York. For helicopters of TKHF flown by HRH The Duke of York, the 3-letter operator designator will be LPD and the radiotelephony callsign will be ‘LEOPARD’.
Note: The rule also applies whenever No. 10 Squadron or No. 216 Squadron aircraft are being utilised for Royal/VIP flights.
4.5 Observation Flights Conducted Under the Treaty on Open Skies
4.5.1
Introduction
4.5.1.1 The Treaty on Open Skies was signed on 24 March 1992 by 25 Countries, including the UK, to promote greater transparency in military activities and thereby enhance international security. The Treaty has now been expanded to include 27 Countries. To fulfil its obligations under the terms of the Treaty, the UK is committed to accept Observation Flights by Observation Teams from any of the signatory Countries over any part of UK territory, including Controlled Airspace.
4.5.2
Observation Flights
4.5.2.1 Observation Flights may be conducted from RAF Brize Norton and Glasgow Prestwick Airport.
4.5.2.1.1 Occasionally, an Observation Flight may overfly several Western European Union (WEU) Countries in one mission – Combined Observation Flight. In this case, the Observation Flight could commence and/or end within the UK, or merely overfly the UK during the mission. Additionally, a refuelling stop within the UK may be required.
4.5.2.1.2 The aircraft used during the Observation Flight may be provided by either the UK or the visiting Country. In either case, a UK Flight Monitor will always be available on the flight deck to act as an interface with ATC agencies.
4.5.2.2 Although His Majesty's Government will receive at least 3 days notice of the arrival of an Observation Team within the UK, the intended route and profile of the Observation Flight (Mission Plan) will not be known until approximately 24 hours prior to commencement. Upon receipt of the Mission Plan, the Airspace Regulation (Utilisation) (AR(U)) will initiate any Danger Area closure action and notify details of the route to the appropriate ATC agencies by means of an Airspace Co-ordination Notice (ACN). AR(U) will also take NOTAM action to notify other agencies and airspace users.
4.5.2.3 Under the terms of the Treaty, aircraft undertaking Observation Flights are to be afforded due priority over other aircraft, (see Note 1) . Observation Flights within UK airspace are therefore granted Category B Status (as detailed in MATS Part 1, Section 1, Chapter 4, para 10C). In addition, when within Controlled Airspace, flights are to be afforded non-deviating status (ENR 1.1.4.2), and when outside of Controlled Airspace, as far as possible flights are to be afforded priority over all other aircraft except those in an emergency or performing roles where the safety of life is involved.
4.5.2.4 All Observation Flights within UK airspace shall be conducted in compliance with published National ATC rules, procedures and guidelines on flight safety, (see Note 2) .
4.5.2.5 For flight safety reasons and to assist in affording priority over other traffic, whilst operating in Class G Airspace, Observation Flights are strongly recommended to remain within the bounds of radio and radar coverage. In addition, to enable the UK air traffic control authorities to meet their responsibilities in accordance with the Open Skies Treaty, in particular the preservation of flight safety, and the prioritisation obligation in Article VI, Section I, paragraph 15, Observation Flights operating in the Scottish Highlands Area are to operate under Instrument Flight Rules (IFR) and remain above the IFR Minimum Levels over high terrain as detailed in SERA.5015(b)(1).
4.5.2.6 The Open Skies Scottish Highland Area is within the area bounded by straight lines joining the following coordinates: 555300N 0050000W – 560400N 0045200W – 560100N 0044200W – 565400N 0022900W – 572800N 0025300W – 572600N 0044000W – 573700N 0043100W – 581300N 0032800W – 583500N 0045500W – 571200N 0062100W – 561800N 0061200W.
Note 1: Treaty on Open Skies – Article VI Section 1, para 15.
Note 2: Treaty on Open Skies – Article VI Section 1, para 14.
4.6 Special Flights
4.6.1
Introduction
4.6.1.1 Special Flight Notifications (SFNs) can be applied to a variety of special aerial tasks which may take place throughout an extended period of time. The most common are Police Authority Air Support Unit (ASU) and Air Operations Unit (AOU) flights, Helicopter Emergency Medical Service (HEMS) flights and HM Government-sponsored flights, (including Ministry of Defence and other flights). The nature of SFN flights is such that they will often require to be afforded priority over most other flights.
4.6.1.2 The purpose of an SFN is to ensure that those ATC agencies likely to provide services to the subject aircraft are aware of any special handling requirements, and that aircraft operators are aware of the conditions under which priority over most other flights is afforded.
4.6.2
Content
4.6.2.1 SFNs will contain details of:
The purpose of the subject flight.
The priority(ies) of the subject flight, to be in accordance with flight categories defined at CAP 493 Manual of Air Traffic Services Part 1, Section 1, Chapter 4 and as authorised by the CAA as follows:
Police Authority ASU and AOU flights - Category A (Police Emergencies), Category B (the normal operational priority) or Category Z (training, test and other flights involving Police Authority aircraft).
HEMS flights - A, E or Z as described in AIC Y 9/2014 dated 20 February 2014.
HM Government-sponsored flights, subject to the nature of the activity but usually Category B for special surveys. Category E applies to time-critical test and training flights, Category Z to all routine training, test and other flights.
The period(s) during which flights may take place.
The period of validity of the SFN.
A Special Flight Notification should normally be issued for no longer than twelve months from the date of issue.
Exceptionally, subject to the approval of the NATS SFN Co-ordinator and the CAA, this period may be extended to no longer than fifteen months from the date of issue when the period of operation of the flight is expected to be longer than twelve, but no longer than fifteen months from the date of issue and/or to assist in the timely administration of notices of renewal.
The name of the operator and the type of aircraft.
The callsign(s) to be used and the main operating base(s).
The routine operating area of the activity.
The operating level (or levels), where appropriate to include minimum and/or maximum levels and/or level bands.
The minimum weather criteria required for the particular operation.
Points of contact for the operator and ATC agencies responsible for the area in which the flight is to be undertaken.
The rules under which the aircraft captain is to operate the aircraft.
Available communications and (if applicable) discrete SSR codes to be used.
Pre-flight notification and co-ordination requirements for the flight, to include the minimum pre-notification period where appropriate or possible.
The action by the aircraft captain in the event of loss of communications (AIP ENR 1.1, subsection 3 refers to basic national procedures).
Any special considerations.
4.6.3
Promulgation
4.6.3.1 Responsibility for the drafting, amendment, promulgation and distribution of SFNs is vested in the NATS SFN Co-ordinator. All queries concerning, and requests for, Special Flight Notification are to be submitted to the:
Post:
NATS SFN Co-ordinator, Room 3115/Box 3115, London Area Control (Swanwick), Sopwith Way, Swanwick, Hants, SO31 7AY
Tel: 01489-444182 (alternate 01489-444181)
Email: special.flights@nats.co.uk
4.6.4
Enquiries
4.6.4.1 All enquiries concerning SFN policy may be addressed to the CAA at:
Post:
Airspace Regulation, Aviation House, Gatwick, RH6 0YR
Tel: 01293-983880
Email: arops@caa.co.uk
4.7 Civilian Formation Flights - ATC Procedures
4.7.1
General
4.7.1.1 ATC will consider formations to be a single unit for separation purposes provided that:
The formation elements are contained within 0.5 NM laterally and longitudinally, and within 100 FT vertically from the formation leader. Within Class G Airspace and subject to ATC approval, these limits may be increased to 3 NM and/or up to 1000 FT vertically.
For the purposes of SERA.3135(d) Formation Flights: Military aircraft flying in formation must be flown at a distance not exceeding 1 NM laterally and longitudinally and 30 M (100 FT) vertically from the leading aircraft in the formation.
The formation, although operating outside the parameters above, has NSF approval.
4.7.1.2 The formation leader is responsible for ensuring safe separation between aircraft comprising the formation.
4.7.1.3 In making initial contact with the ATC unit, the formation leader shall clearly state the number of aircraft in the formation.
4.7.1.4 Where a flight plan is required, the identification of the formation leader and the number of aircraft in the formation must be shown.
4.7.1.5 All ATC instructions and clearances will be addressed to the leader.
4.7.2
Controlled Airspace
4.7.2.1 VFR formation flights by civilian aircraft transiting CTA/CTR/TMA are subject to the normal airspace requirements as detailed at ENR 1.4. All other civilian formation flights in Controlled Airspace are subject to NSF approval.
4.7.2.2 Formations in Controlled Airspace shall be contained within 1 NM laterally and longitudinally and at the same level. Where this is not possible, the formation must be split into individual elements before entering Controlled Airspace. In the event that aircraft within the formation are unable to maintain within these parameters, the formation leader must immediately inform ATC.
4.7.2.3 Prior to entering Controlled Airspace, the formation leader shall confirm that all aircraft within the formation are within 1 NM laterally and longitudinally, and if in level flight, are at the same level.
4.7.2.4 When a formation has been cleared to climb or descend in Controlled Airspace, the formation leader shall confirm that all elements have reached the new assigned level.
4.7.2.5 All aircraft in the formation are to monitor the relevant ATC frequency.
4.8 Air tests with Swanwick(Mil) within the London FIR.
4.8.1 All civil operators wishing to file an airtest using a service provided by Swanwick(Mil) must comply with the following guidance.
4.8.1.1 Ideally, an air test request form is to be sent prior to midnight (local) the day before the test; this is to ensure that Swanwick(Mil) is able to offer a deconfliction service for the civil operator against busy military flying periods. However, should this notice period not be possible, the request to Swanwick(Mil) is to be made no less than 2 hours prior to the airtest commencing. If requests are made with only 2 hours notice then these must be made as early in the day as possible; this is to enable controller workload planning. Requests made late in the day are at risk of postponement until the following day. All pilots should note that the provision of service to any civil airtest is always subject to potential short notice cancellation or delay in the event of unexpected military activity.
4.8.1.2 Captains of test flights are also requested to call the Swanwick(Mil) Supervisor on 01489-612408 (for flights east of the country) or 01489-612417 (for flights in the west), prior to engine start to ensure that the Unit has the capacity to provide an Air Traffic Service outside of the civil airways structure.
Note: The above procedure should only be considered as a request for a service to be provided by Swanwick(Mil) and should not be construed as the filing of a flight plan. All normal flight plan procedures should be adhered to.
4.9 Civil Air Tests within the London FIR and UIR
A test flight is a flight that takes place within CAS that uses the ATS Route network for purposes such as:
Maintenance flights, Demo flights, Fear of Flying flights, Northern Lights, Santa flights, Charity flights etc. This list is not exhaustive.
Requests should be emailed to testflights@nats.co.uk with a minimum of 2 working days’ notice. When submitting a request please ensure the following information is included:
-
Date of Flight;
-
Departure / Destination Aerodrome;
-
EOBT;
-
Callsign;
-
Aircraft Type;
-
RFL;
-
Requested Route (if known);
-
Duration required (if applicable);
-
Any special requirements (for example requirement for a block of levels to be reserved, or unusual manoeuvres);
-
Contact details.
Aircraft Operators may be requested to call the operation before EOBT to confirm final details. Approval for test flights will be subject to operational capacity/traffic and changes to FPLs requested after approval may not be accommodated.
For non-standard flights, please see section 4.1.